Hi everyone, We had developed an iOS Application in Flutter and built it using XCode 26.0.1. We're unable to install this application in iOS 18.7. Below are the details, ➡️ Development Environment: 🔹 Flutter: 3.32.2 ➡️ Build Environment: 🔹 Xcode: 26.0.1 🔹 Build system: Flutter → flutter build ios --release, then opened in Xcode for signing ➡️ Device models tested: 🔹 iPhone (iOS 15.8.3 / 15.8.5) → ✅ installs and launches fine 🔹 iOS Simulator (iOS 18.6 / 26) → ✅ works fine 🔹 iPad (iOS 18.7) → ❌ fails to install ➡️ Error message on iPad (iOS 18.7): 🔹 “Unable to install ‘’. Please try again later.” ➡️ What we’ve tried: 🔹 Cleaned and rebuilt the project (flutter clean, DerivedData removed) 🔹 Deployment Target is set to iOS 18.7 or lower. 🔹 Built the app using an Enterprise distribution profile, not a Development profile. 🔹 Works fine on older iPhones (iOS 15.8.3 / 15.8.5), so signing seems valid 🔹 Device has enough storage, and trust is granted under Settings › VPN & Device Management ➡️ Questions:
Search results for
Apple Maps Guides
149,836 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
The above-mentioned outrage has long since been resolved. If you’re still having problems with this, please reply back here with the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. nitroagility, As it’s been a week since you started this thread, I suspect that things are now unblocked. If not, reply here and I’ll take a proper look at this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
See my response in your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
After upgrading to watchOS 26, users report that when playing music on Apple Watch, if a fitness reminder is received, the music automatically pauses and users need to manually tap the play button to resume music playback. This phenomenon occurs with multiple music and podcast apps. This issue did not exist before the upgrade. We would like to know if this is an Apple bug or if there are any special development configurations needed?
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. Oh, and just FYI: [quote='862770022, glenbot, /thread/771909?answerId=862770022#862770022, /profile/glenbot'] But the first 6 or so i was using the app specific password. I switched to connect api per electron builder recommendations [/quote] The method you use to authenticate has no bearing on the above. I also recommend that you use an API key rather than an app-specific password, but that’s just because it’s easier to understand (-: Oh, and one last thing. I’m going to close out this thread because I don’t want it to become a MegaThread™ that attracts everyone who experiences notarisation delays. If you experience very long notarisation delays — say more than a week — please start a new thread with the details. Put it in the Code Signing > Notarization
Topic:
Code Signing
SubTopic:
Notarization
Tags:
You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. As it’s been more than a week since you posted the above, I suspect that things are now unblocked. If not, reply here and take a proper look at this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
[quote='804029021, rapier, /thread/804029, /profile/rapier'] 2. These should remain in the keychain for as long as the user process is running (just like any other process) [/quote] I’m confused by this comment. They keychain is a per-user persistent database. Stuff you put into the keychain should stick around indefinitely, as long as you’re logged into that user account. Are you able to reproduce this when running these commands from Terminal? Or are you testing this only in some other environment, like a CI system or over SSH? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
[quote='803922021, avinash-iitb, /thread/803922, /profile/avinash-iitb'] Could this ongoing outage be the reason my notarization is stuck? [/quote] That’s possible, but it’s not the most likely reason. Rather, I suspect that your requests were held for “in-depth analysis”. Here’s my standard spiel on that… You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. However, it’s been over a week now, so if things are still stuck then please do write back here with a request UUID and I’ll take a look. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
[quote='862879022, rachelgbarkley, /thread/804484?answerId=862879022#862879022, /profile/rachelgbarkley'] All 7 submissions finished at about the same time and show that they were accepted. [/quote] Cool. I see that behaviour a lot; it’s an artefact of the “in-depth analysis” thing that I’ve described in many other threads here on the forums. The next step is to confirm that your notarised app actually passes Gatekeeper. See Testing a Notarised Product for my recommendation on how to run that test. Hopefully it’ll pass, and you’ll be set. If not, I have a bunch of further hints and tips in Resolving Trusted Execution Problems. And feel free to reply back here if you get stuck. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Code Signing
SubTopic:
Notarization
Tags:
Hello, I have developed an iOS application called DinecTag (be.dinec.DinecTag) with a developer account named Dinec International which is registered in Belgium, I received the NFC entitlement valid for Europe and my App is on the App store since some months (the App is used to open doors by presenting the iPhone in front of a special reader) The App is published only on countries inside Europe (it don’t work outside anyway) I would like my App can be used outside Europe, so I need another entitlement called NFC & SE Platform entitlementn to ask for that, I need an account registered in a country covered by that entitlement Dinec is a company that is member of the Lisam group Lisam has an apple developer account registered to USA, called Lisam Systems So I have asked to the owner of that account to add me as a developer in the USA team So when I connect to my developer account, I can switch between Dinec International SA and Lisam Systems on top right of the screen, I am member of the two teams.
Since around September (iOS 26 release), i'm unable to test my app normally. It says internet connection is required to verify [my certificate id], or just crashing. All terms and conditions accepted, everything is valid, certificates are OK. Reinstallation via xcode does not help. Removal of provisioning profile, generating new does not help. Revoking of certificate and generating new does for around week, then it happens again, but do i need to do it every week now? In logs i see the following: default amfid validation failed because of missing trust and/or authorization (0xe8008026) error amfid not valid: 0xe8008026: The provisioning profile requires online authorization. error amfid Unexpected MISError (0xe8008026): The provisioning profile requires online authorization. default +0300 amfid /private/var/containers/Bundle/Application/5B8E560E-75B2-46EF-8606-02072D99E9CF//Frameworks/oss.dylib not valid: Error Domain=AppleMobileFileIntegrityError Code=-400 An unknown error was encountered UserInfo={NSURL=fil
As the error says, SCRecordingOutput has no delegate property. Rather, you set the delegate when you initialise the object using the init(configuration:delegate:) initialiser. You’ll have to restructure your code to account for that reality, meaning that your startCapture(…) method won’t be able to accept an SCRecordingOutput parameter but rather take a description of how to create such an object, allowing you to then supply your delegate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
Graphics & Games
SubTopic:
General
Tags:
[quote='804786021, milke, /thread/804786, /profile/milke'] So, I came to suspect that I could achieve such bahaviour by using Apple [events] directly [/quote] This is a false expectation IMO. In my experience, the Apple event support within an app is focused on AppleScript. So, the folks working on the app add Apple event support until such time as scripting works well, and then stop. Given that, it’s unlikely that you’ll find ‘easter eggs’ that you can take advantage of by sending Apple events directly. A corollary of this is that it’s best to first get things working from AppleScript and then decide whether you want to run the script directly (using NSAppleScript) or reverse engineer what Apple events it sent [1] and then build and send those Apple events yourself (using NSAppleEventDescriptor). So, in your situation I’d first try to get this working from Script Editor. If you can’t, that’s a sign that you should give up on this approach and explore alte
Topic:
App & System Services
SubTopic:
Automation & Scripting
Tags: