Currently I'm using iOS-app version which I got via TestFlight app (used for testing purposes). For now it's latest version for testing.

As far as I see in another post (e.g. here) current version from AppStore is

Is it possible to push last public version of the app into TestFlight so you don't have to delete beta and install stable?

All I want is to have latest version of the iOS-app via TestFlight until it expires (60 days for each version).


Seems there's a problem with notifications for a new version of app. But also as far as I see:

  • (AppStore) was released on may 5;
  • 1.6.6 (TestFlight) was released on may 10;

So there are five days while beta testers have version that older than other users have. I think this is a little bit odd.

  • Also... most recent version in TestFlight now is 1.6.6 :)
    – Cai
    Commented May 16, 2017 at 14:08
  • @Cai when did you get 1.6.6? I only have Email dated 27 apr for from TestFlight. Don't have iOS device right now to check via TestFlight app. Commented May 16, 2017 at 14:20
  • 1
    Looks like the email for 1.6.6 never came through but TestFlight says it was released on May 10th
    – Cai
    Commented May 16, 2017 at 14:28
  • @Cai will check in a few hours. Thanks. Commented May 16, 2017 at 14:29
  • @Cai I got update to 1.6.6 now. All notifications was been enabled, but I haven't been notified for 1.6.6. Commented May 16, 2017 at 17:14

1 Answer 1


Two parts:

Lack of notifications

I'm not sure why a notification didn't go out, but I think it's a problem with TestFlight and new app versions. Apple recently combined steps in the UI, so now rather than first submitting for approval, then having you go back to add and notify testers after the app has been approved, now you submit your app for approval with a list of testers and check a "notify" checkbox.

So far with the new TestFlight UI, I had only done build version bumps ( ->, which are instantly approved by Apple, and it appears notifications have gone out instantly. It's possible that the delay for review with triggered a bug there. None of that is under my control, however. Hopefully we won't see it with

Why no to the testers?

The only difference between and was updating MathJax CDN locations for both MathJax and MHChem. There wasn't really a need to test it or a benefit for testers (other than testers who use the Chemistry site), so I just sent it to the store without also pushing it to TestFlight. It was a one-off thing but I'll make sure to push the build to testers anyway if it happens again like this.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .