iOS 12; Xcode 10.

User clicks on a button.

2018-09-28 12:14:59.376384+0700 CLAuthorizationStatus: Not Determined
2018-09-28 12:14:59.377407+0700 asking for permission...
2018-09-28 12:15:01.242062+0700 -[AppIosDelegate applicationWillResignActive:]

A panel (alert, whatever) comes up with some text.
But less than a second later:

2018-09-28 12:15:02.163068+0700 -[AppIosDelegate applicationDidBecomeActive:]

and now my app obscures the panel, without giving me time to read it, let alone answer it.

This is not very helpful.
How can this be avoided?

Gerriet.

You can create another window and then display the auth request. When the auth is accepted or denied, dispose of the other window.

On 28 Sep 2018, at 16:54, Alex Zavatone via Groups.Io <zav@...> wrote:

You can create another window and then display the auth request. When the auth is accepted or denied, dispose of the other window.

I have a strong suspicion that this is (again) a case of programmer (=me) error.
Probably the object asking for authorisation did not live long enough.

Sorry for the noise.

On Sep 28, 2018, at 12:48 AM, Gerriet M. Denkmann <g@...> wrote:

iOS 12; Xcode 10.

User clicks on a button.

2018-09-28 12:14:59.376384+0700 CLAuthorizationStatus: Not Determined
2018-09-28 12:14:59.377407+0700 asking for permission...
2018-09-28 12:15:01.242062+0700 -[AppIosDelegate applicationWillResignActive:]

A panel (alert, whatever) comes up with some text.
But less than a second later:

2018-09-28 12:15:02.163068+0700 -[AppIosDelegate applicationDidBecomeActive:]

and now my app obscures the panel, without giving me time to read it, let alone answer it.

This is not very helpful.
How can this be avoided?

Gerriet.