topic Re: Mobile project issues in Xcode in Alfresco Archive

Mobile project issues in Xcode

garryw — Tue, 28 Aug 2012 15:40:19 GMT

Hi,Apologies if this is posted in the wrong forum but has anyone else had any issues with building the alfresco-mobile project?I have downloaded from bitbucket but as soon as I try building the project through XCode I get the following error:Initializing 'GCFloat' (aka 'float') with an expression of

Re: Mobile project issues in Xcode

mikeh — Tue, 28 Aug 2012 15:45:37 GMT

HI

A couple of things to check:

1 - Which version of Xcode are you using? I'd recommend 4.4.1 and also make sure you're targeting the iOS 5.1 SDK.
2 - Are you building the Alfresco target or Fresh Docs? The project contains 3 targets (UnitTest is the other one) but we don't maintain Fresh Docs ourselves; our partner Zia do that. Make sure the left-hand part of the target selector in the toolbar is "Alfresco".

Thanks,
Mike

Re: Mobile project issues in Xcode

garryw — Wed, 29 Aug 2012 08:01:34 GMT

Hi Mike,

Thank you for the speedy reply. I was running an older version of XCode, upgrading to 4.4.1 as you suggested using has worked perfectly.

Thanks again,

Garry

Re: Mobile project issues in Xcode

mikeh — Wed, 29 Aug 2012 08:13:28 GMT

That's great - love the "easy" solutions

A couple of things to be aware of when rebuilding the app from source:
1 - ziadev/master may be unstable at times. We only start heavy QA testing t the end of a series of development sprints. Right now we're halfway through 1.4. You can grab the release-1.3 tag to get the version currently in the App Store.
2 - The version you build won't be able to connect to Alfresco Cloud, as you won't have the private key. We're putting a Public API in place right now, to be released in the coming months. That will work against the Mobile SDKs (iOS and Android) that will also be released at the same time.
3 - For similar reasons the Quickoffice "SaveBack" feature won't operate correctly. You need a partnership agreement with Quickoffice in order to get the required API secret.

Thanks,
Mike