I downloaded the new iOS CQ app on my iPhone 6+ w/iOS 8.4 (12H143), and updated the AXti.me install on my Macbook to 2.3.6. The CQ app opened to a login prompt, in which I provided the IP address of my Macbook and the CQ role password. After tapping go, the CQ screen started to open and then the app closed before it could finish opening. Whenever I tap on the app icon, the screen tries to open and immediately fails again.

The first thing that I did was ensure that the old V1.2 version was removed (it was). I tried changing the CQ password in the event, but the app still will not load. The last thing that I tried was to delete the new CQ app and re-install from the App Store. Same result, it asked for my IP and CQ password, and then closed up shop as soon as I tapped go.

One thing that I just noticed is that the splash screen is still running after the failure if I double-click the fingerprint reader button. I tried swiping it up to close and re-launching with no change of behavior. When I tap on the splash screen to bring up again, it still immediately closes the window.

FWIW, I have Test Flight on my phone if you want to push out a debug version and gather info on what's happening.....

As suspected, somehow the rungroup of James Bottomley is not set correctly. I thought I fixed all entry and edit points, but apparently not. If you simply edit and save that entry in Registration you should be ok.

@Chris - Yup, that fixed it. (Footnote that the problem also happened on iOS 8.0.2 on my test iPhone5, so it wasn't an 8.4 problem.)

We do not use run groups (yet) in the software. After registration, I was playing what-if with the assign run group by class screen, trying to figure out a heat split so that we would have enough workers to cover the course in each group. (With only ~40 drivers at an event, it needs to be more precise to keep things equal.) I did apply it to existing registrations when done.

Even more interesting is that after the event I went and changed the run group labels and re-applied them to everyone. I had originally named them 1/2/3, but some people were getting confused thinking that the run group was a class standing so I changed the group labels to A/B/N after the event and applied it to everyone since they didn't change for drivers just from a re-calculate event. Long story short, the missing driver's run group was apparently missed at least twice, and his class (HS) was most definitely in the red run group on the assign by class screen. I don't think that he was one of the duplicate drivers that I had cleaned up, but maybe that's the case?????