Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

WidgetKit Extension Causing "ITMS-90078: Missing Push Notification Entitlement"
Hello! We have a pretty robust codebase that has APNs enabled for the base app. We recently added a WidgetKit extension to replace our old widget from pre-iOS 14. Our working provisioning profiles (before this addition) were generally as such: Our main target has APNs enabled and configured (and has for ~6 years), testing push notifications on our previous release works as intended Our old widget does not have APNs enabled, since it doesn't support push notifications What we added was: 3. A new iOS14+ widget extension without APNs enabled Ever since we added the third provisioning profile, we've received the warning: ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature's entitlements do not include the 'aps-environment' entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a
0
0
2.2k
Sep ’22
ERROR ITMS-90189: "Redundant Binary Upload.", but the binary is not showing up in TestFlight.
Hi all, I am encountering a problem where I am attempting to upload an IPA to TestFlight using fastlane. In my first attempt, I received no errors. However, even after hours of waiting, there is still no binary on TestFlight for that version and build number. In my second and following attempts, I get this error: ERROR ITMS-90189: Redundant Binary Upload. You've already uploaded a build with build number '18445' for version number '3.66.0'. Make sure you increment the build string before you upload your app to App Store Connect. Learn more in Xcode Help (http://help.apple.com/xcode/mac/current/#/devba7f53ad4). To clarify again, if I go into TestFlight, there is no version 3.66.0. The build number is supposed to automatically increment, as it does previously. So there are multiple problems here for me. Binary not showing up in TestFlight TestFlight thinks the binary is there, so I'm not able to automatically increment build number.
1
0
1.7k
Jun ’22
ITMS-90682: can't contain 16-bit or P3 assets if the app supports iOS 8 or earlier
Hi, I just started seeing this error (without change in assets) in a testflight submission (we have iOS10-only code) - this is the full message (from XCode8)ERROR ITMS-906832: Invalid Bundle. The aseet catalog at 'Paylod/XXXX/Assets.car' can't contain 16-but or P3 assets if the app supports iOS 8 or earlierI can submit by disabling iOS8 but need to know if this is a temporary error, or something wrong in our assets.Thank you
117
0
44k
Aug ’16
Reply to I cannot Upload my App on the Appstore-Please help me
For the first 2 errors: ERROR ITMS-90717: Invalid App Store Icon. The App Store Icon in the asset catalog in 'BBPlayer.app' can't be transparent nor contain an alpha channel. ERROR ITMS-90725: SDK Version Issue. This app was built with the iOS 11.2 SDK. New apps for iPhone or iPad must be built with the iOS 13 SDK or later. App icons can be png. But the size must be exactly the required one. How did you create the images ? For the second, just follow instruction and use 11.3 SDK (that will be the case with Xcode 11.5)
Jun ’20
XCode 10, WatchKit app and distribution error ITMS-90334 with com.apple.wk
I have a project with WatchKit app inside.It used to work smooth with XCode 8 and XCode 9 with automatic signing and distribution. XCode 10 broke something.What i have at the moment is thishttps://i.stack.imgur.com/lJ4Vy.pngERROR ITMS-90334: Invalid Code Signature Identifier. The identifier com.apple.WK in your code signature for myApp Watch App must match its Bundle Identifier com.myApp.watchkitappThe main point here is com.apple.wkIt has been added somewhere at the re-signing stage by the organizer as far as i can understand.I checked my project quadriple and i'm 100% sure it doesn't contain com.apple.wk string anywhere.I switched to manual signing. Created new iOS Distribution certificate. Generated 3 Provision profiles with the correct bundles for app, watch app, watchapp extension. The same error is here.I tried to clean the project, openclose XCode, reboot the system. No luck.I'm unable to dilever my IPA to iTunes with the error above.I tried to export IPA and distribute it with Application Loa
8
0
2.8k
Sep ’18
Reply to Signing and sandbox errors when submitting a Qt mac app. Please help!!
I'm not sure if it's actually possible to publish a Qt app in the Mac App Store. It definitely is; I’ve worked with a bunch of developers in similar situations to you. There are limits to how much I can help you with this. All I can do is explain the requirements imposed by Apple’s distribution channels. When working with third-party tooling, it’s up to the tool’s vendor to explain how best to meet those requirements with their tools. You can find my general advice on this topic in: Creating Distribution-Signed Code for Mac Packaging Mac Software for Distribution after I uploaded to Apple Store Connect through the Organizer, I'd get an email with errors, ITMS-90238: Invalid Signature, mentioning a long list of plugins, and then ITMS-90296: App sandbox not enabled. App Store Connection requires that: All your code be signed with your Apple Distribution signing identity [1] Every executable have the App Sandbox enabled I suspect that your deployment processing has failed to re-sign some of the
Oct ’23