@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.
@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.
@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.
@cjp160 can you please share your project with me so I can test it on a real device with the latest internal Creo version?
@cjp160 test started with the new version. I'll let you know as soon as I can.
@cjp160 after more than 15 hours of continuos testing I can confirm you that the latest version worked perfectly without any crash.
@marco that is great news! Is there any way to get that version sooner than mid-January?
@marco any update on this?
@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.
@marco Do you have a more precise date of when the update will be released? We'd like to plan our launch around it. Thanks!
@cjp160 the official release date is set to January 15th.
Hi @marco - just wondering if the release is still scheduled for today? Thanks
Yes @cjp160 just few hours of delay, so it will probably be tomorrow.
@cjp160 we are already ready to launch the new version but we'll probably have to delay it by another day. I am sorry for the troubles we are causing to you.
Thanks for the update @marco. Would it be possible to send me the version as it stands now so we can start our testing?
@marco I tried running my app with Creo 2.0 and CreoPlayer 2.0 and the app still crashed (after 5.5 hours). I was running making HTTPRequests using HTTPS, and the version you tested used normal HTTP. Is there a possibility HTTPS still has a memory leak? I'm running the test again now using normal HTTP calls.
Hi @cjp160 , I'm trying to debug the issue using the project that you posted on Dec 17 but the HTTP server is unreachable (even changing to HTTPS). Could you please send me an updated version of the project to run in-depth tests?
Hi @cjp160 after further investigation we can confirm you that this is an Apple bug that affects multipart data with a HTTPS connection to a HTTP2 server. We'll soon release an improved version but there is really nothing we can do until Apple will fix that bug.
Can you disable HTTP2 protocol from your server? Alternately, can you use HTTP?
@marco thanks for looking into this further. HTTP works just fine for us, so we are good to go. Thanks again for all the help.