I agree that it should probably work on the public beta
Hence my line about being “over cautious” - I agree that iOS is inherently secure but bugs can and do happen, as you will know. We probably don’t even hear about them being fixed…
1 Like
Nope. I don’t even work in the banking sector for that matter…
That made my chuckle…
It was most likely an old ‘security manager’ that isn’t up-to date with how things actually work made the decision years ago that it will not work on any beta OS and its never been reviewed again cause ‘if it ain’t broke don’t fix it’
I have experience with working with an old ‘security manager’ 
… That’s all I’m going to say 
4 Likes
If I could like that more than once I would 
2 Likes
strange, I never had an issues with Bitwarden on my 13PM
1 Like
Are there apple apps that use it? Only ActivityKit has been made available to developers and so a test flight app would need to be installed that uses it (or an Apple one that already has it implemented). Publicly it won’t be available in the initial release.
See below:
2 Likes
When you run a timer in the Clock app it shows as a Live Activity. I believe the Now Playing controls are technically a Live Activity too. I think those are the only Live Activities on show for now.
The whole “available in a later release” thing refers to third party apps being able to implement them.
2 Likes
They do this all the time. “Universal Control” didn’t appear in the flesh until well down the beta cycle, I don’t really know why
2 Likes
I think this is distinct though. Apple always used to show a timer counting down just that it was smaller.
The “live activity” e.g football scores etc I’m not aware of any apple apps using it yet, I don’t believe it has been implemented?
1 Like
The timer is a Live Activity.
Anyone on the dev (rather than public) beta, have they introduced auto-filling from third party 2FA apps like Authy yet? I’m not seeing in on public.
1 Like
They announced these features as “coming later” at WWDC, they have taken this approach for a while now.
I think it is an improvement on rushing everything out for an arbitrary date in September. There has been much fewer bugs since they adopted this approach, in my experience.
5 Likes
I get that it’s annoying. But I also don’t think it’s reasonable to have any expectation of apps working on a Beta OS release.
This is an implicit part of the deal when using any Beta.
5 Likes
The feature is ready (and working on some Apple apps).
The issue is that devs can’t officially release apps targeting iOS 16 until launch.
3 Likes
Not sure why it being a public beta makes a difference.
Public or Dev, I’d still wager its used by a fraction of a percent of total iOS users.
3 Likes
I agree with @ravipatel 
Not just for support but generally agree it blows my mind when folk expect an app to work on a beta OS. I literally cannot get my head around it.
That being said! @ndrw makes a good point of it naturally breaking vs blocking.
They clearly took the view that they’d rather have an app that works on reduced devices vs an app that might break.
2 Likes
I have no idea about their rationale, but I can see a dev preferring to explicitly remove beta compatibility rather than have to deal with the potential support burden of users wanting beta related bugs fixed.
The above comments kind of demonstrate that many users aren’t understanding of issues when running on betas.
1 Like
It’s not just support requests. You’ll also get however many 1 star reviews from idiots complaining that the app doesn’t work.
I’m not saying I agree with them, just that I can understand why they may have made the choice.
1 Like
For anyone that cares. Public beta 2 is out
4 Likes