Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[iOS] Cannot publish MAUI app to Apple App Store #11465

Closed
petermauger opened this issue Nov 18, 2022 · 4 comments
Closed

[iOS] Cannot publish MAUI app to Apple App Store #11465

petermauger opened this issue Nov 18, 2022 · 4 comments
Labels
area-publishing Issues with the app packaging/publishing process (ipk/apk/msix/trimming) platform/iOS 🍎 s/needs-info Issue needs more info from the author t/bug Something isn't working
Milestone

Comments

@petermauger
Copy link

Description

IPA app packages can be created with dotnet 7.0.100 command line build tools and uploaded to the Apple AppStore. Once a package has been uploaded it undergoes processing. An email is then sent to the Apple Developer team stating:

"ITMS-90482: Invalid Executable - The executable 'APPNAME.app/Frameworks/FirebaseCore.framework/FirebaseCore' contains bitcode."

for every nuget package I include in my project. This same problem occurred with the dotnet 6.0.x command line build tools however you could pass the parameter '-p:EnableAssemblyILStripping=true' to 'dotnet publish ...' and it would remove the bitcode (builds took around 30 minutes). It appears this property is not undertaking the same tasks in dotnet 7 and this causes an inability to publish IPAs to the App Store (kinda important).

Steps to Reproduce

  1. Create a new MAUI app targeting iOS (standard template is fine)
  2. Configure for upload to App Store (valid app ID, certificate, provisioning profile, etc)
  3. run dotnet publish -f:netX.0-ios -c:Release -p:EnableAssemblyILStripping=true where X is any version supporting MAUI but using command line build tools for dotnet 7
  4. Upload ipa file to App Store via Transporter app (on mac)
  5. Note that app is successfully processed and can be made available to testers via TestFlight (for example)
  6. Add a nuget package to the MAUI project - Plugin.Firebase is one example but there are others
  7. run dotnet publish -f:netX.0-ios -c:Release -p:EnableAssemblyILStripping=true again
  8. Upload new ipa file to App Store via Transporter app (on mac)
  9. Receive email from 'App Store Connect' stating that the package contains bitcode

Link to public reproduction project repository

Standard project can be spun up quickly

Version with bug

7.0 (current)

Last version that worked well

6.0.400

Affected platforms

iOS

Affected platform versions

iOS All

Did you find any workaround?

Have tried a number of 'possibly' affecting properties in MSBuild / csproj file but none have the desired effect of stripping out bitcode from attached frameworks.

Relevant log output

Only fails after 'successful' upload to Apple App Store. Response from App Store Connect:
ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/AppAuth.framework/AppAuth' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBAEMKit.framework/FBAEMKit' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBLPromises.framework/FBLPromises' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBSDKCoreKit.framework/FBSDKCoreKit' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBSDKCoreKit_Basics.framework/FBSDKCoreKit_Basics' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBSDKGamingServicesKit.framework/FBSDKGamingServicesKit' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBSDKLoginKit.framework/FBSDKLoginKit' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FBSDKShareKit.framework/FBSDKShareKit' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FacebookGamingServices.framework/FacebookGamingServices' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FirebaseABTesting.framework/FirebaseABTesting' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FirebaseAuth.framework/FirebaseAuth' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FirebaseCore.framework/FirebaseCore' contains bitcode.

ITMS-90482: Invalid Executable - The executable 'AppName.app/Frameworks/FirebaseCoreDiagnostics.framework/FirebaseCoreDiagnostics' contains bitcode.

etc, etc
@petermauger petermauger added the t/bug Something isn't working label Nov 18, 2022
@jsuarezruiz jsuarezruiz added platform/iOS 🍎 area-publishing Issues with the app packaging/publishing process (ipk/apk/msix/trimming) labels Nov 18, 2022
@Redth
Copy link
Member

Redth commented Nov 18, 2022

I think this might be a duplicate of #10989

@petermauger do you have the latest versions of the binding nuget packages that were recently released?

/cc @SotoiGhost

@Redth Redth added the s/needs-info Issue needs more info from the author label Nov 18, 2022
@Redth Redth added this to the Backlog milestone Nov 18, 2022
@ghost
Copy link

ghost commented Nov 18, 2022

Hi @petermauger. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

@ghost
Copy link

ghost commented Nov 18, 2022

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@petermauger
Copy link
Author

Yep, that's an exact dupe of this issue. Annoyingly didn't find it when I searched the error message :(. I'm going to try out some of the suggestions in the linked issue. I'm using latest packages but am including the Firebase frameworks via Plugin.Firebase package (which isn't mentioned in the issue so there may be another way to incorporate the framework).

@ghost ghost locked as resolved and limited conversation to collaborators Dec 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-publishing Issues with the app packaging/publishing process (ipk/apk/msix/trimming) platform/iOS 🍎 s/needs-info Issue needs more info from the author t/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants