Crash reports

  1. ‹ Older
  2. 5 years ago

    marco

    1 Dec 2018 Administrator User since 2016

    @cjp160 we are fixing this issue and a new build will be available soon.

  3. cjp160

    3 Dec 2018 User since 2018

    @marco great, thank you for all the help! Will it be possible to set which devices we want to run on? For example, I'd like my app to work on the iPhone 4.

  4. marco

    3 Dec 2018 Administrator User since 2016

    @cjp160 I am sorry but we really can't support iPhone 4. We made the decision to support iPhone 5S and higher with Creo because Apple officially dropped support for 32 bit apps with iOS 11. Unfortunately iPhone 4, 4s, 5, 5C and iPad 4th Generation use a 32bit only processor and cannot run iOS 11.

  5. cjp160

    4 Dec 2018 User since 2018

    @marco got it, thanks for the reply!

  6. cjp160

    4 Dec 2018 User since 2018

    @marco it looks like the 1.2.6 version of CreoPlayer has been removed from TestFlight. Was this on purpose?

  7. marco

    5 Dec 2018 Administrator User since 2016

    Yes, we found an issue in the 1.2.6 version and so we removed it.

  8. cjp160

    12 Dec 2018 User since 2018

    @marco I'm not sure if you guys have come across this yet, but there seems to still be a memory leak in HTTPS calls. My application still crashes with this beta build and CreoPlayer 1.2.6 if I'm using HTTPS. It does not if I'm just using HTTP

  9. marco

    13 Dec 2018 Administrator User since 2016

    @cjp160 can you please try with the new Creo 1.2.2 version and CreoPlayer 1.2.7?
    Please note that a definitive fix will appear in mid January.

  10. cjp160

    13 Dec 2018 User since 2018

    @marco I ran it last night using just HTTP and the issue seems to be back. That version was working fine with the beta build you sent me and CreoPlayer 1.2.6 but with the latest build and CreoPlayer 1.2.7 it crashed overnight.

  11. marco

    13 Dec 2018 Administrator User since 2016

    @cjp160 the issue is due to the memory warning sent by iOS to the app and ignored in the 1.2.7 build (the GC was disabled). We already fixed the issue in our internal build but we cannot release it because it contains all the new code that will appear in the next major version that will be launched in mid January. Not sure at this point about the best way to assist you. The only option would be to back port all the changes to the current 1.x public version or to open to all the user the current internal beta version.
    Can you wait up until mid January for your app? I assure you that it will not crash in the newer release.

  12. cjp160

    14 Dec 2018 User since 2018

    @marco I built the app using the latest 1.2.2 Creo and uploaded it to TestFlight. So far the tests are working and there hasn't been a crash. Does that make sense based on your knowledge of the problem?

    Waiting until mid-January is really not ideal because we'd like to launch this product within the next week. Hopefully we could find another option if the crash persists.

  13. marco

    14 Dec 2018 Administrator User since 2016

    @cjp160 we fixed several VM related issues in the 1.2.2 build so it makes a lot of sense that your crash has been fixed.

  14. cjp160

    16 Dec 2018 User since 2018

    @marco unfortunately my tests using a TestFlight build ended up crashing. Is there a way to add the building issues to the beta version of Creo (15596) you sent me in this thread? That version worked without crashing.

  15. marco

    16 Dec 2018 Administrator User since 2016

    @cjp160 can you please share your project with me so I can test it on a real device with the latest internal Creo version?

  16. Deleted 5 years ago by cjp160
  17. marco

    17 Dec 2018 Administrator User since 2016

    @cjp160 test started with the new version. I'll let you know as soon as I can.

  18. marco

    18 Dec 2018 Administrator User since 2016

    @cjp160 after more than 15 hours of continuos testing I can confirm you that the latest version worked perfectly without any crash.

  19. cjp160

    18 Dec 2018 User since 2018

    @marco that is great news! Is there any way to get that version sooner than mid-January?

  20. cjp160

    21 Dec 2018 User since 2018

    @marco any update on this?

  21. marco

    21 Dec 2018 Administrator User since 2016

    @cjp160 unfortunately we can't provide a version before mid January. This new upcoming version will be a huge major upgrade and we are not ready to release it now.

  22. Newer ›

or Sign Up to reply!