Re: Build 132 now it's working
Thank you Chuck.toggle quoted messageShow quoted text
Just to confirm, was it restarting your device that seems to have fixed the issue, or did reinstalling initially helped to some extent? And did you initially restart your device after upgrading to 132, or did you only do so after experiencing the issue?
We’re trying to identify what are the minimum and easiest steps that we’d recommend to other users if they have similar issues. So far we’ve found that restarting the device, even though a bit drastic, might be the simplest measure to combat all sorts of unexpected behavior.
Also, what iOS version are you currently running?
On Jul 5, 2018, at 15:53, Chuck Dean <firstname.lastname@example.org> wrote: