EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB321897: MicroStrategy Mobile 10.5 iOS SDK Fails to Upload to App Store with Invalid Provisioning Profile Error


Community Admin

• Strategy


The MicroStrategy Mobile iOS SDK project is downloaded and opened in Xcode. Compilation and archiving is a success without any errors being shown, but when attempting to upload the compiled application to the App Store the errors "Invalid provisioning profile" and "Invalid code signing" are shown.

Scenario
The Strategy Mobile iOS SDK project is downloaded and opened in Xcode. Compilation and archiving is a success without any errors being shown, but when attempting to upload the compiled application to the App Store, errors similar to the following are thrown and the upload is rejected:

  • ERROR ITMS-90159: "Invalid provisioning profile. The app contains an embedded provisioning profile that is not associated with your account. Please use a provisioning profile associated with Team ID XXXXXXXXX."
  • ERROR ITMS-90179: "Invalid Code Signing. The executable 'Payload/Strategy.app/Frameowrks/StrategyMobileSDK.framework/StrategyMobileSDK' must be signed with the certificate that is contained in the provisioning profile."

 
Cause
When the StrategyMobileSDK framework was first compiled, code signing was required and Xcode automatically generated an embedded.mobileprovision file inside the framework.
 
When this framework is used within a project, such as the default Strategy Mobile iOS SDK project, this file shouldbe automatically updated by Xcode when the project is recompiled with a different Apple Developer License.
 
There are two possible causes for this:

  1. Xcode was unable to edit or replace this embedded.mobileprovision file inside the framework, during the compilation process, although no errors were shown until an attempt is made to upload the compiled app to the app store.
  2. Code Sign On Copy is not checked in the "Embed Frameworks" build phase for the StrategyMobileSDK.framework.

 
Solution
Fixing the embedded.mobileprovision issue:

  • Locate the StrategyMobileSDK.framework used by the project, in Finder.
  • Within the StrategyMobileSDK.framework, verify whether a file named "embedded.mobileprovision" exists:
ka04W000000OfvmQAC_0EM440000002GLz.jpeg
  • Delete or remove the "embedded.mobileprovision" file and proceed to the next step to ensure Xcode recreates it during the next build process.

 
Correcting the "Code Sign on Copy" feature

  • Open the Xcode project and click on the project name to view the project targets.
ka04W000000OfvmQAC_0EM440000002GLy.jpeg
  • From the left of the project view, select the target being compiled. If both the iPhone and iPad targets are being used, repeat the next steps for both targets.
ka04W000000OfvmQAC_0EM440000002GM4.jpeg
  • From the top of the project view, select "Build Phases".
  • Navigate to the "Embed Frameworks" build phase, expand it, and ensure that "Code Sign On Copy" is checked.
  • Perform a project clean before trying again, via the "Product" menu in the Xcode menubar.
ka04W000000OfvmQAC_0EM440000002GM3.jpeg

 
Third-Party Software Warning
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 
ADDITIONAL INFORMATION:
The Strategy SDK allows you to customize several Strategy products and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy products or the process of customizing Strategy products, please refer to Strategy Developer Zone (https://developer.Strategy.com).
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@Strategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at https://www.Strategy.com/us/services/support/contact.
CUSTOMIZATION WARNING:
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.


Comment

0 comments

Details

Knowledge Article

Published:

March 30, 2017

Last Updated:

July 17, 2017