Alfresco 2.1(479) on Iphone 4s 7.1.2 exits unexpectedly

[jpbuttet]

Hello,

I just updated a perfectly working Alfresco client to the new (2.1 (479) version.
The phone is iPhone 4s 7.1.2
The working client version was the previous version released on AppStore.
The new one  (2.1(479)) exited unexpectedly upon application launch.

I've tried following:

Uninstall and reinstall the application on the iPhone.
With the clean installation, the application exits unexpextedly without reporting any error message each timne I try to register a new account on iPhone.

I have also tried some dummy parameters, the application keeps exit when I press the register button.

I have my own alfresco server running Alfresco Community v5.0.0
(c r91299-b145) schema 8009 on unbuntu OS.

Any help would be appreciated.

By the way I'd like to congratulate the people that have been investing theirtime working on such a wonderful product (phone client & server)

Best regards.


Jean-Pierre

[mikeh]

Hello Jean-Pierre

Sincere apologies - I know you're not the only person seeing this problem. We have identified an API call that has inadvertently been used that assumes devices are running iOS 8. When attempting to launch on an earlier version of iOS, the API doesn't exist and the app crashes immediately.

We do have the problem fixed and are hoping to submit to Apple tomorrow with a request for an expedited review.

If you do need an immediate workaround, upgrading to iOS 8 would allow the app to run again.

I should mention that, due to some refactoring that we'll need to do to run on iOS 9 later this year, 2.1.x will be the last version of our app that will support iOS 7. Dropping support for older versions of iOS isn't something we like doing, but feel the trade-off between saved development and test time vs. Apple maintaining support for a wide range of devices means this is the right decision.

Many thanks,
Mike

[jpbuttet]

Hello Mike.

Thank you very much for your very good and comprehensive reply.

I'll upgrade to iOS 8.

Best regards.

Jean-Pierre

[mikeh]

I can confirm that the current iOS app, v2.1.1 (487) available in the App Store resolves this issue.

Thanks,
Mike