Unable to submit latest Safari beta to TestFlight

[gorhill]

All is well except when I try to add the latest build to the TestFlight group, I receive a generic "There was an error processing your request. Please try again later" error. I verified and all service statuses for Apple are ok. I feel there is something I am missing -- I do not have much experience with publishing app in Apple store.

I was able to add the same build for a normal stable release, but I want to submit to TestFlight before going ahead for wide distribution.

Any help about this is welcome.

---

This has also happened to other people: https://stackoverflow.com/questions/69822285/app-store-connect-submit-for-review-error-entity-unprocessable-beta-contract-mi

[stephenhawk8054]

Hmm... That's concerning. The next update is important since it addresses the race condition when selecting multiple lists.

Someone said the TestFlight is only available on Mac: https://www.reddit.com/r/uBlockOrigin/comments/1mi8fd6/ublock_origin_lite_for_ios/n73cgta/

[gorhill]

The thing is that this spinner is really useful only for Safari -- something bigger and more intrusive would be visually annoying on platforms where compiling the DNR rules takes less than one second. Anyways it's a first release where we have at least something to really see how long it takes, from there we can see how it's being received by end users.

[stephenhawk8054]

Looks like the compiling happens when adding custom DNR rules too. Should there be a spinner for that process too? Currently the behavior is that the Save button looks stuck.

How about moving the spinner to the fixed part that can be seen on all panes (for example Next to About button, or next to uBOL logo)?

[gorhill]

It's happening from multiple points -- popup panel when toggling "no filtering" mode, develop page, filter lists page, settings page when toggling strict-block, and maybe more. I have given thought about what could be done, but it's not trivial. Ultimately I have been wondering if displaying a special badge on the toolbar icon would be the solution. I don't want to end up adding tons of code paths that are really only of use for one platform. Maybe a noticeable yellow toolbar icon as in uBO at launch -- but this would cause an unpleasant visual glitch on platforms where the registration of DNR rules is virtually instantaneous.

[stephenhawk8054]

Hmm... How about there's a delay between when the compiling starts and spinner/indicator display? After the compiling starts, uBOL waits about 1s and checks again if the compiling is still there. If it is, the spinner/indicator would show. For other platforms, I think after 1s, there's no compiling any more so spinner/indicator would never actually show.

If somehow the spinner actually shows on other platforms, we'll have 1 more symptom to know something's wrong with users' machines/setup.

[gorhill]

Yes, I also was thinking about a 1s debounce. And as for visual feedback, I will experiment with the yellowish icon, it can be seen from everywhere and I won't have to add code paths all over the place.

[dwight1989-coder]

I might be beating a dead horse here but are we still waiting on Apple approval for next UBL release on the App store? thanks for all of your awesome hard work!😁

[gorhill]

Anyways, I will close the testflight group created a while ago that is "broken". I will consider to create a new one on invitation only.