Closed mig35 closed 8 months ago
@mig35 - I was able to confirm this is a bug today in MSDK 11.1.0. Thanks for your detailed report and suggestions. We ought to be able to include this fix in 12.0.0, the next release. Is your app able to work-around this for now by keeping the application class in the default package?
hey @JohnsonEricAtSalesforce thank you for your response. we were able to work around this. anyway do you have any timeline for the 12.0.0 release?
That's great to hear. 12.0.0 doesn't have an exact release date on the calendar, but it is currently in progress and should be available in approximately a month. The fix is in https://github.com/forcedotcom/SalesforceMobileSDK-Android/pull/2513
As previously stated, fixed in #2513
Please fill out the following details:
Version of Mobile SDK Used: 11.1.0
Issue found in Native App or Hybrid App: Native
OS Version: any version
Device: any device
Steps to reproduce: Init SalesforceSDKManager from application class that is located not in the root directory of the project.
Actual behavior: SDK is not able to get BuildConfig value correctly
Expected Behavior: SDK should be able to init correctly and use
context.packageName
, but notcontext.getClass().getPackage().getName()
Error Log: