There are no meaningful changes in package versions between 1.1.7.28 and 1.1.9.28 - the only change is in as-daemon and that change was an icon update.
So now we're investigating lower-level networking changes - of which there were quite a few between 1.1.7.28 and 1.1.9.28. Can I ask a few more questions:
1) have you tried with cellular data disabled, and wireless networking enabled?
2) have you tried with cellular data enabled, and wireless networking disabled?
3) have you tried with both wireless networking and cellular data enabled?
4) have you tried without bluetooth being enabled?
Basically, we're trying to figure out if (for some reason) the network gets into a state where it is reported to the upper-layers that network is not available, halfway through the account creation flow. If so, we need to narrow down precisely the situation which triggers that buggy codepath.
Thanks,
Chris.
↧
