Thanks, What version of the scheduler is this ?
Support Forum
So weird, I can make it crash almost every time I zoom. Exact same setup. Safari on iPhone 15. The only difference is that I saved the link as a 'add to home screen' so it's in standalone mode. Click the share icon and 'Add to Home screen'.
Actually, I just compared the 2 (testing in normal safari vs testing in Standalone safari). It crashes a lot more in standalone mode. hmm...the plot thickens! What is Standalone mode doing that makes it crash much more?
Hi,
I believe this is a recent regression with 6.0.0-beta-2 which is already fixed in 6.0 https://github.com/bryntum/support/issues/9406 . If everything goes well, we are planning to release 6.0 tomorrow or early next week and you can try it in 6.0
Hi Mats (and Alex, Animal & Ghulam),
I hope you are all well and thanks for your efforts thus far to resolve this issue.
I am Nick and the web app that Anuj (Calendardeveloper) is working on is my project.
I am not technical and cannot code myself.
I would like to help co-ordinate the plan of action to sort this out and try to keep it on task because this issue is absolutely critical and integral to the webapp we are developing. Without the ability to zoom without crashing it cannot be launched as it will have no credibility with our prospective customers and it will not be realistically usable in any event. To be clear we do have to drive this issue to a conclusion in order to be able to proceed to launch and it is everyone's interest that we can do so asap. The alternative would be to look at other deployments, or an iOS app. Better we fix the issue as soon as possible if at all possible (it has been ongoing for a fair while now) and we can then launch. We have already invested a lot in our development around this solution and had confidence it would take us to where we need to be.
Congrats on the deployment of 6.0. I can confirm the issue above "not possible to scroll at this time" has indeed be resolved and we can scroll, however I am sorry to say the pinch zoom issue is frustratingly very much still there in full force and the changes in there you thought may have helped have not made any difference.
I know Mats asked for patience while the root cause is found and hopefully it is being investigated as quickly as possible. Are there any updates or news on that? All of our users use iphone. That is the basis of our app. It has to work. If it can work with a few rows then it should also work for more rows and I am sure you also want the scheduler to reliably cater for datasets which are more than just a handful of rows in iPhone safari too. We are in the same boat here.
Yesterday Anuj said: Can you locally turn off the GlobalEvents.touchmove and see if that makes a difference? I am hoping it should be a relatively quick thing to rule out. Rather than wait for the year end for a big refactor."
Do you think you could do this please as this could indeed relatively quickly either rule in or out a long standing inkling that Anuj has about what could be the causing the issue. If so it would be very helpful and I would really, really appreciate it. There is at least a chance that this resolves it, or it might point to other areas to investigate. For our part, we have spent no small amount of development time ourselves trying to help sort this out too, creating the example of it that you requested and also implementing the various different versions to test as per your requests to us. Anyway, now you can easily test anything you think may fix it as Anuj has given you the demo to reproduce it that you requested.
I can confirm it also crashes just as readily in Safari browser (not just the standalone homescreen link) and iphone Chrome too. This is likely because (I understand that) all of these "browsers" are driven underneath by Apple Webkit and the browsers themselves are just "skins" while the machinery underneath it is the same for all iPhone browsers. So the standalone thing is a red herring. It crashes on the normal browser too. 100%.
I guess you guys need to maybe do a deep dive of some sort and rule out with 100% certainty that the issue lies somewhere in your code. If we cannot get to the bottom of it then we do have a problem! The next step presumably for yourselves would be to point out the issue to Apple in their Safari feedback program (do you have a relationship with them?) and ask them to take a look. I am sure they cannot be happy either with their browser crashing as a result of a relatively simple webpage zoom when all other devices do not suffer from this issue, and I am sure you want your software to run reliably on their platform given that so much these days is mobile based and you will have, or will in the future have customers facing the same issues. I know you have a ongoing project of a zooming rework which you had slated for 2nd half of the year and have a POC which you said looks pretty promising, but while that may or may not one day supersede the current zoom handling, we have to sort out this pinch zoom out in the meantime.
Please let me know where we are at and what the plan is. I really hope we can get to the bottom of it and get it sorted out, hopefully resolve it, and finally get the app onto the market.
Thank you for your help and understanding and efforts.
Nick
This one is very tricky to track down as we have no way to debug it. We will try to reach out to Apple to see if they can assist in finding the root cause.
Meanwhile, what if you try commenting these lines in the GlobalEvents.js class:
touchstart(touchstart) {
........
},
touchmove : {
....
},
touchend : {
.........
},
touchcancel : {
.........
},Are you still able to reproduce it then?
Hi Mats,
Thanks for the message.
Anuj will try that, but can you try it also with the example he gave you too please at your end? Would that be okay? Hopefully it won't take you too long and then at least we can have confidence that what you have suggested has been done properly and eliminated from the inquiry.
Have you had dealing with Apple before over Safari or anything?
Do they generally engage and assist reasonably well? Is there hope there?
Also what about the zoom project you were doing? How is it coming along and when is it looking like it will be released? Will it solve these issues for us?
Nick