Distribution to AppStore: Getting "Your app has one or more issues" email but XCode OK

andre_ss6andre_ss6 BRMember ✭✭

I've been trying to solve this issue for more than a week now, searching everywhere, trying everything but I'm out of ideas now. I've compiled my app with a distribution certificate and a distribution profile. Device "IPhone" was selected, not simulator, etc, everything right. When publishing it, it passes on Xcode validation. I even tried the command line validation (maybe it's different from what XCode does?) and it also passes. However, a few minutes later I get an email:

Invalid Signature - A sealed resource is missing or invalid. The file at path [Notificacao.iOS.app/Notificacao.iOS] is not properly signed. Make sure you have signed your application with a distribution certificate, not an ad hoc certificate or a development certificate. Verify that the code signing settings in Xcode are correct at the target level (which override any values at the project level). Additionally, make sure the bundle you are uploading was built using a Release target in Xcode, not a Simulator target. If you are certain your code signing settings are correct, choose "Clean All" in Xcode, delete the "build" directory in the Finder, and rebuild your release target. For more information, please consult developer.apple.com/library/ios/documentation/Security/Conceptual/CodeSigningGuide/Introduction/Introduction.html

I've read about invalid characters being the culprit, but the only thing I have are characters like "ã" and "ç" on the App Store name, which is of course necessary. I can't simply remove the accents. No file at all in the project has special characters in its name. Not even the app name (which is displayed under the app icon after installed). Some C# resource files (.resx) has characters like "ã" and "ç" as well, but I guess that's kinda of expected, right?

Do you guys have any other ideia of what might cause this or how can I discover the underlying issue?

Answers

  • ColeXColeX Member, Xamarin Team Xamurai

    It may caused that you updated the macOS , the file system got changed.

    Check the solution jacargentina provided in this thread : https://forums.developer.apple.com/thread/89187

  • andre_ss6andre_ss6 BRMember ✭✭

    Thanks @ColeX. I had seen that thread. Unfortunately for me though, I use MacInCloud and they use APFS. Do you know if there's any workaround I can use?

Sign In or Register to comment.