The new iTunes Connect distinguishes between the internal testers (maximum of 25) and external testers (maximum of 1000).
At various points they say that newly uploaded builds are automatically distributed to internal testers via the test flight app, and this has usually been my experience. But sometimes I see a menu like this, indicating that I need to select "Invite Testers" in order for it to be visible to internal testers:
What causes this?
When it does this, I cannot distribute my build to my internal testers, and it seems like iTunes Connect is failing to recognize that my project already has internal testers.
We've been experiencing this too. A hack that works for us sometimes is turn the TestFlight Beta Testing switch off, then wait for that to take effect, then turn it back on, and it usually pushes the latest out to the internal testers.
Turning the "Test Flight Beta Testing" switch off and back on will indeed change the "Internal" column to Active. As #will suggests. The problem is that if you are already approved for External delivery, this will also cause the external testers to go back to the Submit For Beta App Review again, so use this work-around with care.
Related
I'm trying to send my app to External TestFlight testers. All the tutorials mention that I should be able to add external testers via an External Testing tab on the left hand side. I don't see this option.
I tried filling in all the details in "Test Information" but I still don't see the section.
How do I see the External Testers section for my app?
I resolved this by creating an Internal Testing group first. After doing this, I was able to see the plus sign near the External Testing header on the left hand side.
Note: There's also a chance that I didn't need to create this group, and simply waiting 15-30 minutes caused it to appear.
We have uploaded an update of our existing app (WASFAT) as internal testing build. We can access it successfully.
Now I want to leave from the internal testing and want to access the live build.
There is not leave button the playstore wasfat page. Please have a look at the attached image.
When we have released beta version, we had that leave button. But in the internal release, we don't have it.
How can I get out from this internal testing mode? How can I access the original live build? Also I don't want to remove my id from play console internal testing.
Thanks for any suggestions
As far as I know, you can opt-out of internal testing with the same link you used to enter in the internal testing program. Also, you need to remove your email from internal tester. However, It will take some time to be able to access live mode again
The simplest way I have found is to just switch to a different account within play store.
Open play store afresh
On top right, tap your account icon (or where ever it is located)
Click the drop down and tap "Add another account"
Later on it is just a matter of selecting an account, no password entry needed if done before.
The advantage of this is that you don't have to wait for Googles services to register that you have disabled a testing account. When you need to enable the testing account you will have to wait again. So this is pretty nifty for me.
I'm reliably able to restart my phone, and have changes to beta status reflected immediately.
advertisingIdentifier is different for apps from the same vendor.
Of course there is an ability to add apps into group and share some "unique string". But I suppose that there must be some easier way.
I also read about "Uniquely Identifying a Macintosh Computer" but I suppose that such apps are rejected in mac AppStore.
In our app we access the system serial number. We use it to try prevent multiple users using the same account + for debug purposes (so not for ads or anything, our app has none).
We also have code to access the hardware uuid but that code isn't actually used at the moment, but it is in there, so not sure how deep Apple checks. So you might be able to use this one too. As an additional step you could hash either of these (or hash them appended or something).
This app has been on the AppStore for a long while now, and was never rejected for this reason. So I'd say accessing this data on macOS should be ok (for now) depending on usage and safe to submit to the app store.
Keep in mind that in some rare cases, the serial number will not be available. In that case we store a random string in UserDefaults.standard and use that cached value in the future.
Since this information won't be available to your 'other' app(s), this workaround won't work for you though.
Pardon all the italic shouting. Just trying to emphasize key points. Please note that the existing post iOS app submission and beta review process does not answer this question.
The following sequence of events does happen and it's what I expect:
Create a new version (number) of app in iTC
Archive and upload app to iTC
Internal testers get notified to download with TestFlight
Submit for Beta Approval (critical for next step)
Now all testers (inside & out) get notified to download
But next:
Create a new build (number) in Xcode
Archive and upload to iTC
Only internal testers are notified. ⬅︎ unexpected
Do I need Beta Approval every time I want the external testers notified? I could swear this has not been the case. But of course things may have changed. Or it's just my bad memory.
Do I need Beta Approval every time I want the external testers notified?
NO
I could swear this has not been the case. But of course things may have changed. Or it's just my bad memory.
It's just that:
1) there's a short delay (5-20 minutes) before you can send to external testers
2) from time to time Apple's servers are screwed, and the 5-20 minute delay becomes "many hours".
Change the version number - you have to wait for a (presumably human) approval: takes 1-2 days
Change the build number - only a short delay for a (presumably) automatic check.
And don't forget you have to manually release to the external testers each time!
You need to approve first build of every new version.As Apple mentioned" A review is only required for the first build of a version. Subsequent builds may not need a full review.."https://help.apple.com/itunes-connect/developer/#/dev3bfa33892
Beta review is only required for the first build and the first build send in after a 90 day period.
I'm submitting my first app through iTunes Connect. It is a social networking community so I have to provide a demo account for the submission. My app already has a live database of users as there is currently an active web version.
I'm new to this and confused as to how I should handle this. Should I be creating a demo account that will not show up in any other live user's search results? Are the testers going to be attempting to interact with other live users? I am assuming I will need to show the various functions of the app, like messaging and events. In that case should I be creating a few "demo" users for the testers to interact with?
Alternatively, should I be linking them to the development version and development database? If that's the case, then the build that I send them would only be a development build then?
I am confused on how this is supposed to work and can't seem to find any information to help?
In my experience, you'll need to give them the production version that will go into the store. So not the development build.
When we submit an app for approval, it seems to get installed and activated on a couple of devices, but nothing much ever happens. They barely use it, as far as we can tell. We can tell that it's installed and run. We have previously been rejected when the network connectivity wasn't working right, so we know that they do look at the app after it's installed.
I'd suggest you make them an account that looks relatively anonymous (or even "Test Account" which you real users are hardly likely to try to interact with). You could create another account and say "If you want to send a message, send it to account xxxx". We've never had them interact with our app enough to utilise the suggestions we've made.
If you have an active / inactive flag, you could think about making these accounts inactive once the app is approved, then re-activating it when you next want to submit your app.