I make no claims that this is the best way to do things, or even a good way. I just wanted to share the way I have started doing this now, because I think it allows you to do some cool stuff and handle caffeine apps just like they are your own, you still arn’t the controller but it starts to feel closer to that.
This may have been obvious to you guys, but I only recently figured this out.
Prompt:
Hardcode the admin principals. There are 3 valid admin principals
(replace with actual pids)
1. your-II2.0-pid-in-draft-app
2. your-II2.0-pid-in-live-app
3. your-dfx-pid
these hard coded principals, must be included in userProfiles Map by default or they won't work, because they won't be registered.
what are your questions?
This prompt will make admin auth handling smooth, for some reason it can be wonky if you don’t do this. and also it lets you use your developer principal to call any method in your caffeine app.
just to show you it works:
oh and that backend canister id its just a test app, its nothing special. I already deleted it. ![]()
