Mobile SDK Upgrade From 2.3 to 3.0

-
Compilation and Linking Issues

Upgrading Salesforce Mobile SDK from 3.1 to 3.2 is indeed quite simple

$ cd <your_Cordova_app_folder>
$ cordova plugin rm com.salesforce
$ cordova prepare

But every time I did the upgrade from 3.x to latest version of SDK. I see the following set of errors.

Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_SFHybridViewController", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SFDefaultUserManagementViewController", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SFUserAccountManager", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SFLogger", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SalesforceSDKManager", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SFLocalhostSubstitutionCache", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SFPushNotificationManager", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
  "_OBJC_CLASS_$_SFHybridViewConfig", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
ld: symbol(s) not found for architecture arm64

And you see the following binaries (.a) files are missing.


Under "Compile Sources" InitialViewController.m was missing.


Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_InitialViewController", referenced from:
      objc-class-ref in AppDelegate+SalesforceHybridSDK.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)



Also, please note that there used to be two modules for networking.

libMKNetworkKit-iOS.a
libSalesforceNetworkSDK.a

Now, libSalesforceNetwork.a replace them both.

Resolution

I started off by linking the missed libraries manually.

Link the binaries under "$(SRCROOT)/OneStop/Plugins/com.salesforce"  in Build Phases.  Also, don't forget to add InitialViewController.m under compile sources.
I also added CDVDevice.m to resolve the plugin error.

IT Worked!!

Soon, I faced a roadblock. Once I authorize the app, the screen is stuck at "Loading" view. "Create Passcode" screen never comes up in iOS 8.3 OR intermittently comes up in  older version of iOS 8.

I thought there should be a fix in unstable branch. I downloaded the source code of iOS SDK (https://github.com/forcedotcom/SalesforceMobileSDK-iOS) and generated libraries by running SalesforceSDKCore and SalesforceSDKCommon projects in "Release" mode. In order to run in release mode, I edited the scheme to select "Release" mode for Build Configuration.



Once done, pickup files from "Release-iphoneos" folder. You can navigate to the folder by looking up for the .a file under "Products" folder in Xcode.




I copied all the files to $(SRCROOT)/OneStop/Plugins/com.salesforce and linked them again. This time I made sure names and link order match with the sample apps.

It worked!


If you want to do this in a simple way, just navigate to com.salesforce plugin repo (https://github.com/forcedotcom/SalesforceMobileSDK-CordovaPlugin) and copy the libraries. The task of importance is to make sure you have correct libs and right linking order.

Comments

Post a Comment

Feedback - positive or negative is welcome.

Popular posts from this blog

Updating SourceData/ Data Source of the Pivot Table

-
Image
Errors:  1. Run time error '1004' Cannot Open PivotTable source file https://....[servlet.FileDownload?]... 2. Data source reference is not valid 3. Can not use web data source as pivot data 4.  Run-time error '-2147024809 (80070057)' Item with specified name wasn't found 5.  Error: Cannot open PivotTable source file ‘[filename[x].xls]SourceData’ 6.  Exception from HRESULT: 0x800A03EC   at System.Dynamic.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, UInt32 argErr, String message)    at CallSite.Target(Closure , CallSite , ComObject , String )    at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)    at CallSite.Target(Closure , CallSite , Object , String )    at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1) Solution: We have spend a day searching around for the solution. We get this error when we open the excel sheet
Read more

Salesforce.com migration tool - Deploying Weblink and migrating files with special characters

-
Image
Recently, I noticed the followed issues in SFDC Ant deployment. Issue 1: Typo in XML <name> metadata data for Web Link Just to reiterate, all the buttons and links created under "Buttons and Links" section of the Object are treated as Web Links . Screenshot from Force.com Migration Tool Guide It should be WebLink, not Weblink. Otherwise, the following error occurs while extracting the package :  package.xml - Entity type: 'Weblink' is unknown. Correct XML is:  <types> <members>Opportunity.Cancel_CheckOut</members> <members>Opportunity.Generate_Deal_Sheet</members> <name>WebLink</name> </types> Issue 2: Unable to deploy entities with special characters Example: <types> <members> User w/Export  </members> <name>Profile</name> </types> I tried to deploy Profile entities with special characters like '-' and '/
Read more

Information Architecture - Setup your term store to scale

-
In this post I am going to put together a list of best practices to consider when setting up a term store in Sharepoint Online. As you may already know term store is collection of term groups. And each term group consists of number term sets. Each term set contains a list/hierarchy of terms. Team group gives the flexibility in terms of access. You can assign permissions to users on their term group, rather than giving them access to the entire store.  Always maintain a corporate/general term group which contains common term sets across organization.  Every group/business unit should have a term group. Pin the terms from corporate term group as required into Business unit term groups.  For example, you plan to maintain list of document types in common term group. Thus, there is a term set created. Marketing department want to use this term set. But, they want to add a few more terms. In this case, you should create another term set in Marketing department term group and pin the te
Read more