Search results for

ITMS-90158

1,686 results found

Post

Replies

Boosts

Views

Activity

invalid code signing error in embed framework with error ITMS 90046
Hi,We have a main project which use a custom embed framework. The framework has a bundle identifier com.example.test. The main project has different one. When we make ipa for adhoc, it works fine and can install on the iphones as well. But when we upload the ipa with application loader for Testflight it gives the below error -ERROR ITMS-90046: Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'TeamID.com.org.domain' for key 'application-identifier' in 'Payload/MyApp.app/Frameworks/EmbededFramework.framework/EmbeddedFramework' is not supported. This value should be a string starting with your TEAMID, followed by a dot '.', followed by the bundle identifier.According to this error, we use the same bundle identifier in framework's info.plist and in build settings. It resolved the error but another issue is raised when we download/install the app on iPhones. The app is not able to installed on iPhon
2
0
2.5k
Dec ’15
ITMS-90338: Non-public API usage
We have developed the iOS App using .NET MAUI, when we try to upload it to store, the binary is getting rejected with the following error, kindly suggest a solution for this. TMS-90338: Non-public API usage - The app references non-public symbols in : _ubrk_openRules, _ucal_add, _ucal_close, _ucal_get, _ucal_getAttribute, _ucal_getKeywordValuesForLocale, _ucal_getNow, _ucal_getTimeZoneDisplayName, _ucal_getTimeZoneIDForWindowsID, _ucal_getWindowsTimeZoneID, _ucal_open, _ucal_openTimeZoneIDEnumeration, _ucal_set, _ucal_setMillis, _ucol_close, _ucol_closeElements, _ucol_getOffset, _ucol_getRules, _ucol_getSortKey, _ucol_getStrength, _ucol_getVersion, _ucol_next, _ucol_open, _ucol_openElements, _ucol_openRules, _ucol_previous, _ucol_safeClone, _ucol_setAttribute, _ucol_setVariableTop, _ucol_strcoll, _ucurr_forLocale, _ucurr_getName, _udat_close, _udat_countSymbols, _udat_format, _udat_getSymbols, _udat_open, _udat_setCalendar, _udat_toPattern, _udata_setCommonData, _udatpg_close, _udatpg_getBestPattern, _udatpg_
0
0
355
Sep ’23
Reply to Direct link to all my apps in App Store not working in iOS 12
Honsetly, your best bet is to: go to some reputable app's website look for their Get it on the App Store button Inspect said button, and figure out what the current url format is (Tried looking my app up on the iTunes Link Maker.... My app has been released for 3+ years, the link maker couldn't find it... >.>) As of writing, this format works: itms-apps://itunes.apple.com/app/id1234560377 itms-apps://itunes.apple.com/app/id If you log into https://appstoreconnect.apple.com you can get your appid from the url: https://appstoreconnect.apple.com/apps//appstore/info
Topic: App & System Services SubTopic: Core OS Tags:
Nov ’20
ITMS-90338: Non-public API usage
Hello, We contacted Apple Developer Support due to an automatic message we receive when trying to publish a new version of our app The app links to non-public libraries in Frameworks/UnityFramework.framework/UnityFramework: /System/Library/PrivateFrameworks/AVFCore.framework/AVFCore. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. The problem is we do not understand what the issue is even when reading your automatic message. How can we debug this ? How can we identify the source of the problem ? Do you have any idea of what the problem is ? What we tried : We tried to re-publish the application we currently have on your store (production) with different build number => App rejected with the same automatic message ; We tried to look fo
2
0
591
Jul ’23
Apple App Store Submission rejected with code ITMS-90748 and no other information.
I built and submitted a react-native app and the app was sent to Apple for submission. I received an email back 5 minutes later that reads Dear Developer, We identified one or more issues with a recent delivery for your app, TYPSA REGISTRO DE JORNADA 1.0.2 (1.4). Please correct the following issues, then upload again. ITMS-90748: ${message} Best regards, The App Store Team The ${message} looks like a template placeholder that isn't populated and thus there is no information indicating what might be wrong. I google searched for the specific error code and could not find anything. What does this code mean and why is my app submission failing?
1
0
731
Jan ’23
ITMS-90620: Invalid iMessage App - Your iMessage app contains an invalid sticker pack.
Problem Description: ipa trial, get feedback from Apple ITMS-90620: Invalid iMessage App - Your iMessage app contains an invalid sticker pack. The app may have been built or signed with non-compliant or prerelease tools. For more information, go to developer.apple.com. Since we added sticker (Messages Application Extension) we checked There is no problem with bundleid of ipa and bundleid of sticker We found that hxl.xcarchive contains the MessagesApplicationExtensionSupport folder, and there is a file named MessagesApplicationExtensionStub in it But we did not include the MessagesApplicationExtensionSupport folder after exporting ipa from hxl.xcarchive Our command line to export ipa is: xcodebuild -exportArchive -archivePath build/20230203_130051/hxl.xcarchive -exportPath build/20230203_130051/ -exportOptionsPlist ExportOptions.plist
1
0
381
Feb ’23
ITMS-90725: SDK Version Issue - But I'm using an SDK which meets the guidelines in the message!
I received an email with the following message from Apple: ITMS-90725: SDK Version Issue - This app was built with the iOS 15.5 SDK. All iOS apps submitted to the App Store must be built with the iOS 15 SDK or later, included in Xcode 13 or later. Well, what's the problem Apple? I used 15.5. That's later than 15!
2
0
856
Mar ’23
ERROR ITMS-90362 Submitting watch OS2 app with Healthkit to iTunes Connect
Have been trying to upload an archive of our app and watch app to iTunes Connect which includes support for iOS9 and watch OS 2 with healthkit.I keep running into this error:ERROR ITMS-90362 :Invalid Info.plist value. The value for the key 'UIRequiredDeviceCapabilities' in bundle {bundle name} is invalid. Expecting array with a single string value of watch-companion'In order to get our app working since it relies on healthkit, we have included healthkit in our UIRequriedDeviceCapabilities and without it the app will never load.<key>UIRequiredDeviceCapabilities</key> <array> <string>healthkit</string> </array>Using this causes the app to not be able to submit. If i change the string to 'watch-companion' as it seems to suggest, then the watch app will never start.Here is an image of the error when uploading through Organizer:https://cloud.githubusercontent.com/assets/1257664/9561131/c6a5b56e-4e30-11e5-9817-3b3d8614e1c5.pngHas anyone been able to submit a watch OS2 ap
28
0
4.6k
Aug ’15
ITMS-90626: Invalid Siri Support - Sample phrase 'Play Fan on deep sleep sounds' cannot contain 'fan'
After a successful app delivery I received the email from App Store Connect. It says: Dear Developer, We identified one or more issues with a recent delivery for your app, XXXXX. Please correct the following issues, then upload again. ITMS-90626: Invalid Siri Support - Sample phrase 'Play Fan on deep sleep sounds' cannot contain 'fan' ITMS-90626: Invalid Siri Support - Sample phrase 'Find Fan on Deep Sleep sounds' cannot contain 'fan' ITMS-90626: Invalid Siri Support - Sample phrase 'Play Fan on Deep sleep sounds' cannot contain 'fan' .... and some more all complaining about 'fan'. I couldn't really find anything on Google related to Siri Support and cannot contain. Does anybody have idea what could be wrong? Thank you!
0
0
595
Apr ’23