• State Verified Answer
  • Replies 13 replies
  • Subscribers 20 subscribers
  • Views 648 views
  • Users 0 members are here
Options
Related

This setting will reduce battery life

Valeriy Kovalenko
6 days ago

Some users of my app have started seeing this screen when they launch the app (sorry for the quality — this screenshot was sent by a user):

They get stuck on this screen.
My question: where can I find any documentation about it? I can’t reproduce it in the simulator or on my own device (Descent MK2). I don’t really understand how to fix it.

Since this appears to be a system screen, I would expect the green button to return the user to the app — but it seems like I may need to handle that manually somehow.

Kind regards,

Valeriy

  • 0 5 days ago in reply to FlowState

    maybe the bug is in the documentation that SENSOR_PULSE_OXIMETRY was added accidentally to OnboardSensorType instead of RemoteSensorType?

    Strangely OnboardSensorType is claimed to be present since 1.0.0 while the only 3 values it have are present only since 3.2.0. And then I didn't talk about the strange values 6,7,8...

  • 0 5 days ago in reply to flocsy🤠

    Yeah that would make the most sense haha

  • 0 5 days ago in reply to flocsy🤠
    flocsy🤠 said:
    Strangely OnboardSensorType is claimed to be present since 1.0.0 while the only 3 values it have are present only since 3.2.0.

    Oh that's nothing new. It's the same for some of the other enum types in the docs, like Activity.TimerState or ActivityRecording.Sport2 (yes I know it's deprecated).

    I suppose technically it's not wrong, as what seemingly really matters is the API level that their names/values were introduced.

    Maybe the idea is that you can still refer to those enum types on devices with older API levels? There are other enum types which are documented to exist starting at API levels much higher than 1.0.0. (Ofc most forms of type checking will disappear at runtime, except for has and instanceof. I have no idea if instanceof is supposed to work with enum types or not). Yeah I really have no idea, and I don't really feel like investigating this.

    flocsy🤠 said:
    maybe the bug is in the documentation that SENSOR_PULSE_OXIMETRY was added accidentally to OnboardSensorType instead of RemoteSensorType?

    As with other documentation errors of this nature, it's not just a doc error, it's also a type check info error.