nullpixel
Add sideload support
Few ways I can do this:
- Allow manual ECID input on the first attempt, and cache for the rest (easiest)
- Find another private API to get the ECID.
@AppleBetas your input on this would be liked, since it's evident we cannot get the ECID from inside the box of sand. I could ask the user once and store it somewhere?
Not sure if possible but you could:
- Bundle mobile configuration profile that gets user ECID in app
- Start temporary server and host profile
- Redirect user to profile
- Have URL of profile send data back to app's server, which then redirects it to a URL scheme such as tsssaver://ecid/ECIDHERE
I'd say storing the ECID would be convenient, but User Defaults carry over with backups and it's possible that even after switching the device, the user could still get the old device's ECID
I didn't think that mobileprovs. actually allowed for getting ECIDs. Also, starting a webserver would require the personal VPN entitlement which is paid, so we'd have to host that somewhere in the cloud, which may not be a big issue.
You can always just start the server and access it from DEVICE_INTERNAL_IP_OR_LOCALHOST:3000.
I think it only has to be from another device when installing apps (what happened with Extender)
Ahh, makes sense then. Yeah, I don't see why this'd be an issue, although it could get cumbersome doing it repetitively. How about caching it, and the UDID, and if the UDID has changed then we can re-get the ECID?
We can't get the real UDID inside the app without these hoops either, though.
Ah yeah, that's a valid point too. I'm just not sure from a UX perspective we should be doing this process every time. There's no longer any truly unique IDs now, is there?
I was going to suggest the keychain, but that syncs.
Not that I'm aware of. How often does the user use TSSSaver though? The process is like 30 seconds with this added loophole, so it's not like it is a terrible compromise
Yeah, that's a good point. I'll add google analytics / fabrics to track users and we can see if it's even worth removing the loophole
@nullpixel No one needs your code. I am enough smart to make it myself :P
