Switching servers on iOS crashes application on data refresh

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Configuration, iOS
• Labels: None
• Environment: iOS 5.1 (9B179) iPhone 4S ; iOS 5.1 (9B176) iPad ; XCode iOS 5.0
• Similar Issues: Show 4 results ; ;

  MOBILE-282	Pull to refresh causes crash when application is not configured
  MOBILE-80	Liferay Sync on iOS either crashes or doesn't load file list
  MOBILE-225	Sometimes the application crashes when download is canceled
  MOBILE-269	Application crashes when removing a favorite by swiping

1. Connect to server1. Refresh documents.
2. Connect to another server. Refresh documents. Liferay Sync crashes.
3. Liferay Sync crashes at launch when establishing internet connection.
4. Disable internet connection. Liferay Sync launches.
5. If we revert the server config with internet disabled. And then re-enable internet, liferay Sync launches. Liferay Sync also pulls down the data from the first server just fine.
6. Rebooting the device by holding the sleep switch and sliding to turn off doesn't resolve it.
7. Reinstalling the application allows for you to join any server.

I think it has to do with storing the server ID and it is looking for that at launch.
Attached is the iPhone crash log.

[Randall Hidajat]

This is resolved using 1.1 on iOS

[Caleb Fong]

Thanks Randall!

I'll write up a doc for the customer portal.

[Bruno Farache]

Hey guys, I was able to reproduce on 1.1. Just committed a fix.

[Bruno Farache]

Maybe for some reason you were lucky and got the same groupId for both servers, Randall.

This issue happens because groupId is cached in the app and when you switch the server and there's no Group with the same groupId, it throws:

Caused by: com.liferay.portal.kernel.repository.RepositoryException: No Repository exists with the primary key 19.

You should test different servers with different dbs.

[Caleb Fong]

Hi Bruno,

So the issue happens when the groupID for the servers are different?
Should we reopen this ticket?

Thanks,
Caleb

[Bruno Farache]

That's right, you guys should check the console on the server side.

No need to re-open the ticket, I just committed the fix.

Thanks for all details Caleb, they were very helpful.