iRule is closed on iPad after opening

Since a few days I have had the problem that iRule wears out on my iOS devices after opening them. So I can't use it anymore. However, it still exists as a task. If I turn off my Wlan it works without problems. Does anyone know the problem?

I have the same problem - starting happening a few day ago also. Especially when I go to a page on my iPad remote that contains the Vera module. iRule just shuts down. I haven't made any changes to this remote in a long time and it was working fine. Any ideas?

Same problem with a new installation without config. No matter on which iOS device. On Android it works without any problems.
I think the problem is somewhere in my network. Like I said, I turn Wlan off it works. It also works in another Wlan network. Something's bothering the app.

the iPads not working are running iOS 9 with the new version of the app not working on them.

i have an iOS 10 also with the old version of rule on it. i'm afraid to update it.

on my iOS 11 devices the old version of the app is obviously working and the new version of the app is also working on iOS 11.2.2 to be exact. i didn't do the newest iOS update yet. i'm donning that on another iPad right now to experiment. i'll report back.

Ok, I've now invested a little more time and noticed something ongoing. The problem has nothing to do with the iOS version. It's much more of a network problem. I have turned off all my access points and activated only the FritzBox as a wireless router. The app runs without problems. From the moment I activate another AP in my network the app closes. The APs I use are Ubiquiti Unifi. I also connected a Fritz repeater once, with the same result. So as soon as my Wlan is distributed over several APs I get the problem.
I'm coming up with something even more creazy. I have a guest wlan in addition to my normal wlan network. Here iRule runs without problems. That's really weird, isn't it? I have now released the required devices for the guest wifi and can now use iRule again.
With Android the error does not appear.

I will say this, after about a weeks worth of working on it, and posting in their forum, it is spot on and yeah, it can do everything iRule can do without a question. I have already built my old remote from iRule in it and no complaints. They do things differently which did take some learning. But it is pretty darn powerful! I ended up purchasing the $30 upgrade as I needed more than one device to be controlled. I have two GC controllers in my setup. If you don't need more than one, it is pretty much free!

This little fiasco with iRule pushed me over the edge and have already uninstalled iRule on my iPad. Just using the builder to see how I had things going and for some of the commands. No complaints.

Pretty sure it is a problem with the app but can't hurt to try this while you're waiting on iRule to fix this problem.

All of iRule's best programmers have surely been working on Kramer's version, they probably assigned the iPhone 7/8/X update to some new guy, who must not have tested it in an environment with more than one AP.

Latest version does not fix the problem with older IOS versions. My previously working iphone 4 running 7.1.2 no longer works. This is super frustrating. I bought 2 used iphone 4s to replace the no longer supported ipad touches a few years back. Now I'm back in the same spot.

Same issue and situation for me as Andy.Zartman... using iphone 4 as a dedicated remote (for a delayed 1 hr shut off timer, since that requires the app to be running and locks it up until executed), and same iOS (7.1.2). Quit working just 3 days ago, and no luck getting it back up. I tried removing and reinstalling the app, resetting the network connectivity, etc.

Another ploy to upgrade older hardware? Apple wouldn't do that, would they...:)