İOS 26 beta battery %1

[quote='857997022, lucky06, /thread/799833?answerId=857997022#857997022, /profile/lucky06'] send the demo project and app [/quote] I took a look at that today and I’m confused by your starting point. My general advice when building Mac software is to do your day-to-day development using Apple Development signing. Then, once you have things working, you can export your app using the signing appropriate for your distribution channel (Apple Distribution for the Mac App Store, Developer ID for direct distribution). See The Care and Feeding of Developer ID for more about this. If you do that then you only need to worry about the -systemextension stuff at the final step, when you export your product for distribution. And when you stick with Apple Development signing you can rely on Xcode’s automatic code signing to do the right thing. However, you seem to be trying to use Developer ID signing for day-to-day development. This is a mistake, and it’s causing you grief here. So, for example, I opened your project today

OK, a quick update… IMPORTANT Please don’t post replies that just say ‘me too’. There’s a Boost button at the top of the thread that you can click in that case. OTOH, if you have new info to share, please post a reply, not a comment. It’s hard for me to keep track of comments. My understanding of this issue is that: It was a problem with the way that the Developer website issued provisioning profiles. It had been resolved at the time I posted that response, about 4:00 Pacific time. Hence my original advice on this thread to run a test with a new, unique bundle ID. I just ran that test myself and I didn’t see a problem. Specifically: Using Xcode 16.4 on macOS 15.6.1, I created a new project from the iOS > App template. In Signing & Capabilities, I confirm that automatic code signing was enabled with my team selected. I selected an iOS 18.6.2 device as the run destination and chose Product > Run. The app ran just fine. However, this is using my extant wildcard provisioning profile, s

[quote='858241022, Siamprodhan, /thread/800521?answerId=858241022#858241022, /profile/Siamprodhan'] 3- Navigate to the Trust section and set it to Always Trust. [/quote] I’m not sure why that helped in your case but this is not a good idea. Modifying certificate trust settings is a common cause of errSecInternalComponent errors. I’m back in the office and I’m gonna take another look at this again once I have a few minutes to spare. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

The bug still exists in the latest XCode 26.0 (17A324) and with the latest simulator images iOS 26.0 (23A343)

I'm guessing this has something to do with the new versions of Xcode and iOS that were in the middle of... Just got pushed an update.

Was struggling for hours before discovering this thread. The issue for me was for literally any app i tried to upload, not just one specific app. I did discover a workaround. WORKAROUND: Go to Certificates, Identifiers & Profiles Create a profile that specifically targets your app bundle identifier create the profile, download it disable automatic profile management in xcode under Signing & Capabilities Import newly downloaded profile worked for me :)

Yeah I'm glad I'm not the only one. At least the iPhone simulator is working just fine.

did you also experience this issue after the ios 26 update?

I can validate that behavior. Basically following all that there is on the next few pages -> https://developer.apple.com/documentation/wifiaware/building-peer-to-peer-apps after one device become subscriber and the other publisher in a while the same application will want again devices to pair with pin otherwise they will never connect.

Hi Ed, Thanks for the detailed response. I’d like to clarify one point: my app is still using the UIApplicationDelegate lifecycle and not the scene-based lifecycle. Could this duplication be related specifically to using the AppDelegate lifecycle rather than the scene lifecycle? If so, is there a recommended way to handle or prevent the duplicate delivery without migrating to the scene lifecycle? Thanks in advance for your guidance.

People say sometimes, 'You work in the fastest-moving industry in the world.' I don't feel that way. I think I work in one of the slowest. It seems to take forever to get anything done.