@eskimo
What makes you think that’s necessary?
Xcode produces this message. One could be forgiven to think that you have to go into Settings > VPN & Device Management and find that darn certificate.
Btw, at the same time the device itself shows an alert saying "Unable to verify app", and something about "An internet connection is required to blah blah...." - Of course the device has an internet connection.
So far, none of the suggested remedies have helped.
Post
Replies
Boosts
Views
Activity
For more context, my app has received the transaction and has finished it. I received these messages from storekitd:
[66BBGGXX] Finishing transaction 0123456789 for com.blah.myapp
and
StoreKitServiceConnection(***): Returning 0 products, 2 invalid identifiers for com.blah.myapp
Everything is back in working order now.
Yes, the picker will list individual applications. You have to use them first for them to show up
Yes, you can set up different restrictions for individual devices.
While I'm not presenting a "solution", it should help with perseverance.
I have the same problem, with some twists.
Sorry, not an answer, just a me too
In my app, this has always happened, regardless of iOS version. I didn't start testing install/delete until later in my development but it has definitely happened in iOS 15.4. Not only does it not allow the app to be un-installed, it will also often cause the authorization process to fail in an odd way. Like the parent auth shield comes up, I supply the info, then the center.requestAuthorization closure completes with success. However, any call to any Family Controls or Device Activity function will result in "This app has not been approved for Family Controls" or similar error.
It will successfully install on a device that has been reset (Erase all content and settings), and the app will work as expected... until I try to delete the app, which fails.
I have built a separate minimal test app with the 3 extensions and one schedule and one monitored activity... It works perfectly, I can install it and delete it as often as I like.
So there is something amiss in my app, and I see the error that the OP mentions all the time in the device logs and the console logs.
Anybody have any idea what "recordName" this error refers to? This wouldn't have anything to do with the length of the bundle ids?
I have created several FBs for this issue and Apple's responses didn't lead anywhere.