Welcome!
This is the community forum for my apps Pythonista and Editorial.
For individual support questions, you can also send an email. If you have a very short question or just want to say hello — I'm @olemoritz on Twitter.
Pythonista 1.6 beta Is available again!
-
No longer crashes on boot.
-
I'm sorry, I've uploaded a new build more than 12 hours ago, but it's somehow stuck "processing" on the server side (second attempt already). There isn't much I can do right now...
-
Understood. I will wait for the upgrade email.
-
Searching Twitter reveals that there seems to be an ongoing issue with TestFlight.
-
Same problem here. Just emailed about it prematurely. Says expired 12 hours ago in test flight.
-
Still "processing"? Apple says that TestFlight is up and running on their developer system status page. Should someone report this to Apple?
-
Did some quick research and came across [this][] question regarding the issue.
[this]: http://stackoverflow.com/a/28871948 -
One question: Will Pythonista retain its prior save data after a valid provisioning profile is installed once more, or will I be required to restore everything from Dropbox?
-
From past experience, user files are retained.
-
Same, I've never lost any files with Pythonista beta updates.
-
Oh, ok. Thanks.
-
Ditto.
-
Nonetheless, make sure to back stuff up, just in case! You could try accessing the files in Pythonista on your computer with a program such as iMazing or iFunBox. It helps even if you don't want to update anything (I once accidentally deleted my entire script library with StaSh, though it was entirely my fault for using
rm -rin the wrong directory). -
Yes! If you're in the beta, please make a backup. It is actually quite likely that the next build will require a clean install (i.e. you'd need to remove the old version first).
-
@omz - @polymerch just started another thread asking how to do a backup when you can't run Pythonista. I think your comment may have caused some concern that the TestFlight expiration issue will cause us to have to do a full reinstall since we may have been caught offguard and not done our normal backups when this happened.
Just to be clear - I am assuming that you will get past the TestFlight deployment issue soon and the build we get is not going to force a clean install - correct? I am also assuming that if something else happens and we have to blow away TestFlight, we should still be able to just reinstall the 1.5 and see our existing scripts and data. So there is not much need for concern.
We understand that something unexpected may happen and we should be prepared and backed up and when the formal 1.6 comes out we may need to restore everything at that time. This TestFlight glitch has just hit us a bit by surprise.
-
I've uploaded a "new" build with a different version number, let's see if that helps. If it works (i.e. if you see a TestFlight notification within the next 24 hours or so), you probably won't lose data when you install it (though it obviously doesn't hurt to have a backup anyway).
There are some other changes I'm still working on, and regardless of this whole mess, it's likely that one of the next builds will require a clean install, but I'll try to not make that coincide with the expiration of the previous build, so you can prepare for this better.
-
I was not having problems relative to the test flight issue, just with git and github. I am using iMazing for full backups and transferring. Works real well.
-
Looks like it actually worked. :) The new build should be available now. Again, no actual changes, but the next one will be more interesting...
Sorry about this, I could have seen it coming (not the first time TestFlight has server-side issues), and I should have prepared for this by submitting the build sooner...
-
Any plans to send out a new batch of beta invites with this new build?
-
Got the build, downloaded, still have all my stuff. :)
