App controls unresponsive for 'event' and 'scenario' about easer

[renyuneyun]

Strange, I can't reproduce this problem...
I tried

1. create a new Scenario
2. create a new Event
3. edit a Scenario
4. edit an Event

They all work without problem...

[craftyguy]

Hmm. I'm on Android 8.1.. do you have an 8.1 device to try this on, or perhaps the emulator?

Later on when I have more time I can reproduce this on my device with logcat going to see if there is anything interesting printed there.

[renyuneyun]

Well, it's an Android 8.0.

I'll try to test it on an 8.1 emulator later.

[renyuneyun]

Hmm, do you know any 8.1 emulators? I can only find ~8.0.

[craftyguy]

I don't know of any, if the official android emulator thing from google doesn't support 8.1..

I recorded my screen showing this issue. Unfortunately the app I used to record the screen does not show screen taps, but the sections of the video towards the end when nothing is happening on the screen are me actually tapping the controls at the top of the app (back, menu, save).

https://craftyguy.net/pub/recording_20180127_113905.mp4

[craftyguy]

I have figured out how to easily reproduce this: when prompted to allow calendar access to Easer, deny it. Then when you swipe past the calendar widget in a new event, the interface becomes unresponsive.

IMHO, users should be able to deny permissions to Easer for certain things without it breaking. For instance, I will never use the calendar feature and so I want to disable the permission for it to minimize any potential data leaks if easer were ever to be compromised.

[craftyguy]

@renyuneyun
A potential fix for this is to disable plugins for which Easer does not have permission to access data for.

For example, if I deny calendar access to Easer, and uncheck the calendar plugin in Easer, I do not hit this issue. Is it possible to have Easer automatically disable plugins when it is denied access to the data that the plugin needs?

[renyuneyun]

Thanks for the info. Now I have a guess of the potential cause.

Actually there is some problem in the handling of the post-request signal. I had a plan to revise that part later, but now it may be the time to check it.

[renyuneyun]

I suppose v0.5.5 would alleviate this problem. Is that the case?

[craftyguy]

It seems like it does! Thanks for the quick fix!

One small suggestion to make it more user friendly, instead of just graying out the option, it might be better to also display a message that this option isn't available because Easer was not granted the permission. This way the user can see the direct result of denying a permission, and they may have even forgotten they denied it in the past.