omz:forum

    • Register
    • Login
    • Search
    • Recent
    • Popular

    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!

    Pythonista
    15
    51
    37344
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • omz
      omz last edited by

      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).

      1 Reply Last reply Reply Quote 0
      • wradcliffe
        wradcliffe last edited by

        @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.

        1 Reply Last reply Reply Quote 0
        • omz
          omz last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • polymerchm
            polymerchm last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • omz
              omz last edited by

              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...

              1 Reply Last reply Reply Quote 0
              • JonB
                JonB last edited by

                Any plans to send out a new batch of beta invites with this new build?

                1 Reply Last reply Reply Quote 0
                • misha_turnbull
                  misha_turnbull last edited by

                  Got the build, downloaded, still have all my stuff. :)

                  1 Reply Last reply Reply Quote 0
                  • omz
                    omz last edited by

                    @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...

                    1 Reply Last reply Reply Quote 0
                    • dgelessus
                      dgelessus last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • wradcliffe
                        wradcliffe last edited by

                        @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.

                        1 Reply Last reply Reply Quote 0
                        • Saturn031000
                          Saturn031000 last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • ccc
                            ccc last edited by

                            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.

                            1 Reply Last reply Reply Quote 0
                            • Gerzer
                              Gerzer last edited by

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

                              1 Reply Last reply Reply Quote 0
                              • ccc
                                ccc last edited by

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

                                1 Reply Last reply Reply Quote 0
                                • zencuke
                                  zencuke last edited by

                                  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.

                                  1 Reply Last reply Reply Quote 0
                                  • polymerchm
                                    polymerchm last edited by

                                    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.

                                    1 Reply Last reply Reply Quote 0
                                    • dgelessus
                                      dgelessus last edited by

                                      @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.

                                      1 Reply Last reply Reply Quote 0
                                      • polymerchm
                                        polymerchm last edited by

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

                                        1 Reply Last reply Reply Quote 0
                                        • misha_turnbull
                                          misha_turnbull last edited by

                                          Has there been a new beta version yet?

                                          1 Reply Last reply Reply Quote 0
                                          • briarfox
                                            briarfox last edited by

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

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Powered by NodeBB Forums | Contributors