June 20, 2018 at 9:33 pm #50778
The iPad/iPhone app is freezing when launching app when it is already up. If I kill the running app it will launch, but freezes second time.
Or start a station manually the stop the station and it usually freezes.June 27, 2018 at 12:22 am #50851
Same when running app on iPhone.June 28, 2018 at 2:23 pm #50881
Same here. Both iPad as iPhone freeze when app is opened and iPhone / iPad is not used for a few minutes and goes to sleep automatically. All wakes up after opening, except Open Sprinkler….. I can only “repair” that by shutting down and restarting iPad and/or iPhone. Great app, really, but this is so annoying…… thanks for a solution!July 2, 2018 at 4:39 pm #50920
I’ve been having the same problem since April or May 2018 (when we turned the sprinklers back on. I don’t think it was happening back in Oct. 2017.
Still happening on version 1.7.8July 4, 2018 at 4:23 pm #50938
Yep, same here. On iPhone X, not sure if that matters.
But I don’t think the app is frozen, it just isn’t accepting any touch input from the screen.
It seems that it is still running though.
Been doing lots of tests with our irrigation lately because it is getting hot, and the freezing app has been a problem.July 8, 2018 at 1:57 am #51023
Is this still an issue? Last time I chatted with Samer, he said this has been fixed. If it’s still happening let us know. Thanks.July 8, 2018 at 7:20 am #51025
Yes, still happening.
iPhone 7, iOS 11.4, App version 1.7.8.July 17, 2018 at 2:36 pm #51174
OK, I will check with Samer again about it. In the meantime, a work-around is to open a web browser and directly type in the IP address of OpenSprinkler — you can access OpenSprinkler either through the mobile app, or directly using a web browser like Chrome.July 22, 2018 at 9:09 am #51242
We have had several reports via support and here on the forum of this issue and working towards resolving it. However, reproducing this issue has been difficult. If you can provide any reliable steps to reproduce this it would help tremendously in solving this.
I will update this thread as I gather more information.
Currently, I have verified the app is not doing anything on resume so not sure what would cause it to lock up. One idea I am exploring is moving to WKWebView (currently using UIWebView).July 22, 2018 at 9:34 am #51246
I can reliably reproduce the issue. Here’s how:
1. Start app.
2. Manually start one station for 5 minutes
3. With app still on the screen, lock iPhone by pressing power button once.
4. Wait at least a minute or two.
5. Unlock iphone by pressing home button/fingerprint reader.
6. app is still be on screen, but I am unable to press anything.July 22, 2018 at 9:45 am #51248
@Jeremy Thank you for that! I can see exactly what you mean now. All click/touch input stops working. However, slide gestures seem to continue to work. This is odd indeed. I will start debugging now, thanks!!July 22, 2018 at 9:46 am #51249
For me, it is a little less specific to reproduce. I don’t necessarily have to start any stations. Sometimes just opening the app will have it freeze.
I will mention, I’m on iPhone X, not sure if that makes any difference … but seen a similar issue with another app after they updated it to allow for the larger screen.
I would say that 9 times out of 10, I can get the “freezing” to happen from just normal use. But like Jeremy, letting the screen sleep and then unlocking it back into the app is almost surefire way to do it.
Hope any of that rambling gibberish helps. 🙂
~LazJuly 22, 2018 at 9:53 am #51250
Great, glad that helped.
btw, I did test with just opening the app, not running a station, and letting it sleep, but it didn’t seem to (reliably) reproduce the issue.July 22, 2018 at 10:03 am #51251
Thanks Jeremy, Samer! Loooking forward to the update!July 22, 2018 at 10:27 am #51259
Okay found the issue: It’s due to FastClick library using incorrect values for the timestamps. Here is more detail:
I am trying out a fix now, if it works we will push this out ASAP.
Thanks!July 22, 2018 at 3:26 pm #51277
Just to update everyone, from my testing the fix works and is now in review as version 1.7.9. Hopefully this will address the issue however please let me know if anyone continues having the issue after updating.
Thank you for your patience!July 23, 2018 at 3:48 pm #51306
Version 1.7.9 is now available in the store. Please let us know if it resolves the issue.
Thanks!July 23, 2018 at 4:24 pm #51307
This update appears to have resolved the issue. I am no longer able to reproduce it with the steps I posted yesterday.
I’ll let you know if it occurs again. Thanks!
- You must be logged in to reply to this topic.