function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Kyle Roberts 1Kyle Roberts 1 

SFRestRequest failure on mobile SDK 2.3 and iOS 8.3

As of iOS 8.3, the call [[SFRestAPI sharedInstance] requestForDescribeWithObjectType:] does not ever return. The app does not crash, freeze, or hang, just escapes out of that method. In the screenshot below, the first breakpoint is hit many times for each operation we have created yet the second breakpoint is never hit. In iOS 8.2 and below, it works as expected (hits both breakpoints).

https://www.evernote.com/shard/s302/sh/589ce78b-409b-4861-ba13-ab97068c0331/d8bdbb7747ec20adfb7211d179473a49

Best Answer chosen by Kyle Roberts 1
Gaurav KheterpalGaurav Kheterpal
I can reproduce this successfully with a sample app from the 2.3 SDK. You can try posting this to the official Mobile SDK Google+ communinty page (https://plus.google.com/communities/114225252149514546445) but I'm pretty sure that you'll be recommended to upgrade to 3.1.

On the same note, is there a reason why you're still on 2.3 - considering that it's quiet old now.

If my answer helps resolve your query, please mark it as the 'Best Answer' & upvote it to benefit others and improve the overall quality of Discussion Forums.

Gaurav Kheterpal

Developer Forums Moderator| Certified Force.com Developer| Dreamforce Speaker| Salesforce Mobile Evangelist
 

All Answers

Gaurav KheterpalGaurav Kheterpal
I can reproduce this successfully with a sample app from the 2.3 SDK. You can try posting this to the official Mobile SDK Google+ communinty page (https://plus.google.com/communities/114225252149514546445) but I'm pretty sure that you'll be recommended to upgrade to 3.1.

On the same note, is there a reason why you're still on 2.3 - considering that it's quiet old now.

If my answer helps resolve your query, please mark it as the 'Best Answer' & upvote it to benefit others and improve the overall quality of Discussion Forums.

Gaurav Kheterpal

Developer Forums Moderator| Certified Force.com Developer| Dreamforce Speaker| Salesforce Mobile Evangelist
 
This was selected as the best answer
Kyle Roberts 1Kyle Roberts 1

Thank you for your reply. I actually did end up asking on the Google+ page after I posted here and we did find the answer there. The fix was released in a recent update of 3.x and my team was able to cherry pick what we needed. As for still running 2.3, it is what the project began with and there has not been any push or budget to upgrade.

Here is where we ended up with the information we used.
https://plus.google.com/113038836091854379566/posts/6pfHDZBJZrL