@eskimo I might have the same or a related issue. Can you elaborate a bit on my issue? https://developer.apple.com/forums/thread/697226

Suggestions from this thread (https://stackoverflow.com/questions/69267550/ios-15-untrusted-developer-issue) on disabling automatic signing, closing Xcode, removing existing profiles, restarting Xcode, reenabling automatic signing (recreating the profiles) doesn't help. Due to incompatibility on code signing between iOS 14 and iOS 15. Even not with a new custom provisioning profile. This seems like a bug on iOS15 - it's no longer possible to debug apps on offline devices. Apples war on 3rd party jail breakers seem to yet again be in the way of decent honest paying developers. Sad.

Apparently this is a known problem in iOS15. A workaround this is creating a paid developer subscription. This is not an acceptable work around and this needs to be fixed asap. https://developer.apple.com/forums/thread/690728

I have this problem too with a paid developer program membership. I'm NOT creating another Apple ID and paying for another developer program subscription to work around this. Have anybody found a solution? iOS 15.2 on iPad 8th gen. Xcode 13.1 on MacBook Pro (Silicon)

I think I've found a solution for this. Apple seems to have change code signing from iOS14 -> iOS15. Automagically created certificates is of the type "iOS development" and for som reason when these are used on iOS15 they need online verification on every launch. Deleting my developer certificate and creating a new one of the new type Apple development, solved my issue. The code signing now only has to be done online at the first launch - just like in the good old days. I'd wish that Apple would stop messing with the code signing. Every time they do, they make these crazy edge case fuck-ups. For me the proper fix was to delete provisioning profile and development certificate and create a new of the "new" type "Apple development"

I think I've found a proper solution for this. Apple seems to have change code signing from iOS14 -> iOS15. Automagically created certificates is of the type "iOS development" and for som reason when these are used on iOS15 they need online verification on every launch. Deleting my developer certificate and creating a new one of the new type Apple development, solved my issue. The code signing now only has to be done online at the first launch - just like in the good old days. I'd wish that Apple would stop messing with the code signing. Every time they do, they make these crazy edge case fuck-ups. For me the proper fix was to delete provisioning profile and development certificate and create a new of the "new" type "Apple development"

Actually there is a huge difference in the new and the old certificates. Apple jinxed it again again. I'm developing an app that is connection to a device via WIFI without internet connection. The initial development was done on Xcode 13.1 and an iOS14 iPad. That worked well. As usual the iPad needed to be on a WIFI with internet connection at the first launch to verify the code signing. After that it was fine to launch the app from Xcode to the iPad while it being on the WIFI without internet connection. The app didn't need any additional code signing verification. After updating the iPad to iOS15 every launch started to fail with the error unverified when the iPad was on WIFI without internet connection. Launching on the iPAD on WIFI with internet connection was fine. It seems like iOS15 causes apps to verify code signing on every launch - not only the first any more. After searching and fiddling with Provisioning Profiles for several days I found out that Apple now has two different types of certificates - an "iOS Development" certificate and a "Apple development" certificate. The latter being the "new" thing. Deleting my automatically created certificate and creating a "new" - and then a new provisioning profile solved my problems. My app now only needs to verify code signing at the first launch. This difference (and the change in iOS15) should definitely be more obvious - or even better: not have been an issue by making the certificates compatible.

At least my issue was the result of Apple again messing with the code signing creating a ling tail of side effects. iOS15 code signs differentially on the "new" type of certificates. I'm developing an app that is connection to a device via WIFI without internet connection. The initial development was done on Xcode 13.1 and an iOS14 iPad. That worked well. As usual the iPad needed to be on a WIFI with internet connection at the first launch to verify the code signing. After that it was fine to launch the app from Xcode to the iPad while it being on the WIFI without internet connection. The app didn't need any additional code signing verification. After updating the iPad to iOS15 every launch started to fail with the error unverified when the iPad was on WIFI without internet connection. Launching on the iPAD on WIFI with internet connection was fine. It seems like iOS15 causes apps to verify code signing on every launch - not only the first any more. After searching and fiddling with Provisioning Profiles for several days I found out that Apple now has two different types of certificates - an "iOS Development" certificate and a "Apple development" certificate. The latter being the "new" thing. Deleting my automatically created certificate and creating a "new" - and then a new provisioning profile solved my problems. My app now only needs to verify code signing at the first launch. This fixed my code signing / developer verification issues.