Forum Archive

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.

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 -r in 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. :)

@JonB I'll send out a new batch of invites with the next build. The thing is, I anticipate that the next build will require a clean install if you have the current beta installed, but not if you're coming from the App Store version, so it doesn't really make sense to add new testers right now because that would increase the risk that someone doesn't read the release notes carefully enough, and loses data...

Downgrading to the public version isn't possible without a full reinstall I assume?

@omz - Glad to see that the TestFlight update finally worked. No issues or data loss here.

Thank you for the clarification and the suggestions on how to backup and prepare for the next build. I hope all beta testers will use this opportunity to test their disaster recovery strategy. Anyone can have a device go bad and brick on them, so this is a good thing to do in any case. As per your suggestion, took a look at iFunBox (Win7 version) and found it to be a great product. I also use the existing scripts to routinely do a zip file local backup and upload it to Dropbox.

@dgelessus - You can actually downgrade to the public version by going to the App Store searching Pythonista and then tapping the cloud download button. It retained my data when I did it just after the beta expired.

Perhaps @Saturn031000's approach above should be the recommended way to do the upgrade to the NEXT Beta release. That is, drop back to the App Store version and then do the NEXT Beta upgrade.

While the previous Beta was nonfunctional, I was able to successfully back up all files with the free versions of both iExplorer and iFunBox. Thanks for the suggestions. They worked like a charm.

@ccc Good idea, I think I’m going to try that.

Easter Sunday... Once again, crashes on boot.

Sigh!!! The app opens then crashes. It is still in my list of running apps but when I select it it flashes and quits. Test flight says beta expired 6 hours ago.

So, I saved my documents folder via iMazing and re-installed 1.5. Saving was not necessary, but I've learned to cut the cards. Lost nothing but a curious observation.

Under 1.6, the iPhone 6 reports ui.get_screen_size() of (320,568), but under 1.6, it reported (375,667). A challenge to us lazy types who hardcode location/dimensions for ui components. @OMZ: Also a little weird.

@polymerchm, that is not weird at all. Apps that do not support a device's native resolution are instead run at a lower res, but displayed slightly upscaled by iOS. From the app's point of view the screen size is the emulated one, not the physical one, because it wouldn't be able to handle the real screen size. That's why the small size emulation happens in the first place. Pythonista 1.5 doesn't have largeyPhone support yet whereas the 1.6 beta does, that's why you're noticing a difference in the perceived screen size.

So I suspected. Guess I have to do it correctly and detect the "real" suppoted screen size. Or wait for the next beta.

Has there been a new beta version yet?

I'm showing expired 3 days ago, Crashing on load.

I went into the Apple AppStore and downloaded the v1.5 version and it flawlessly performed the downgrade from v1.6 beta to v1.5 preserving all of my scripts. I can not use the v1.6 capabilities but at least I have a working Pythonista that no longer crashes on load.

I was also able to downgrade as @ccc suggested, without losing any data. :)

Strange, when I check the App Store for Pythonista, it just shows the normal "open" button instead of the cloud redownload icon. Tapping that button tries to open the app, and fails as expected. Was this changed with the iOS 8.3 update?

For me it behaves as @dgelessus said. I'm on iOS 8.3 as well. The app crashes on boot.

Same here - iOS 8.3 FUBAR'ed all available paths to downgrade without losing data. Can't downgrade via the AppStore (showing "OPEN" button). Can't backup the Documents folder.

I shouldn't have procrastinated....(in hopes that Ole would push another beta build) :(

I guess I snuck in under the wire. Downgraded before 8.3 fiasco.

Just successfully installed (downgraded) Pythonista.ipa v1.5 using iFunBox's "Install App" and didn't lose any data!

Thanks for the 8.3 tip. I was just about to upgrade iOS but was able to downgrade Pythonista first without loss. It wasn't that big an issue because I am fully backed up. Now anxious to get Bluetooth BLE again.

So I'm just wondering what exactly is going on with 1.6? Is there a new beta coming or is it going final? Thanks.

I expect between new glitches due to 8.3 and tidying up loose ends, 1.6 is plodding. Wouldn't surprise me if OMZ has a day job too!!

Ole doesn't seem to have posted in any of his normal haunts (forums, blog, twitter feed) since April 1, several days before the beta expired. That is very unlike him. Even if he doesn't have an immediate fix for some issue he usually comments. It is rare that he doesn't comment on something in one forum or other every couple of days. I hope he is OK.

He's tweeting. Last on the 17th. So my opinion stands.

@polymerchm I was expressing concern, not trying to contradict your opinion. I'm happy to be wrong. It is not a debate. I just hope the long silence in these forums doesn't mean he is sick or something. I still remember Fabio Varesano.

DIdn't mean to sound combative. Not sure about the person to whom you refer, but if its a loss of someone who frequented the forum, my apologees.

@polymerchm Sorry to be touchy. Fabio was a 28 year old grad student that created the open source FreeIMU and FreeIMU library. One day he stopped posting on his forum and weeks later we learned that he had a quite unexpected heart attack. As a result when people suddenly disappear from Internet locations I get a bit worried. I'm sure he has other things on his plate but it is really very unlike Ole to not respond. I looked but didn't see activity on his twitter account because I didn't see the "tweets and replies" button. (I'm not a big twitter user.) He has only replied since March (no tweets) and those weren't displayed by default. If I had seen those I wouldn't have been worried.

The new release is planned?

Please see this

Please see that ;-)