You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Getting started with the boilerplate repository (https://github.com/hotwired/turbo-ios/tree/main/Demo), I am trying to configure a turbo-ios application to connect with rails 7. Everything works fine on most advance and replace actions, except that some links are broken in the iOS context. Those specific links work on both iPhone Safari and web browsers.
My problem seems quite similar to the one described here : #3
When the link is clicked through the simulator app, the request is sent to the web server, executed and rails returns a 200 status. However, the view from the simulator throws an error (after staying stuck on the loading screen for a few seconds). Clicking the retry button actually loads the page (cf. screenshots 1 & 2).
For example, in the index page below, clicking on the main link (i.e. "MRH-L de Dora Holder") will trigger the error, but clicking on the ellipsis dropdown and on the "informations" dropdown item will load the page properly. But those two links point to the same exact URI. They alse have no "data-turbo"="false" attribute and no data-turbo-action attribute either because I want to advance (actually adding the "data-turbo-action=advance" instead of implying it doesn't work either).
The structure of this page is the following
each row is loaded in a turbo_frame with a src attribute pointing to the show page
each row contains
links to the show page
the dropdown ellipsis.
Clicking the ellipsis will lazy-load the menu items from a lazy-loaded turbo_frame pointing to the object show page as well.
I don't know if this structure could have an impact on my issue.
I also made sure that my JS console doesn't throw errors on those specific pages that don't load. Once again, they work fine in other contexts (web browsers, safari) and after clicking the retry button as well. It really seems like the advance redirection mechanism, and probably the configuration of my app, are causing the issue.
Most links advance or replace, work fine. Only a few actually throw this error. And this will happen even if I don't change anything to the boilerplace (except the local variable in Demo.swift). But I can't figure out the pattern that will throw the error.
Any help would be greatly appreciated!
Thanks,
The text was updated successfully, but these errors were encountered:
These are example logs from Xcode on a failed request. I cannot figure out why does turbo cancels the visit though, and how to troubleshoot this issue?
Hi! Getting started with the boilerplate repository (https://github.com/hotwired/turbo-ios/tree/main/Demo), I am trying to configure a turbo-ios application to connect with rails 7. Everything works fine on most
advance
andreplace
actions, except that some links are broken in the iOS context. Those specific links work on both iPhone Safari and web browsers.My problem seems quite similar to the one described here : #3
When the link is clicked through the simulator app, the request is sent to the web server, executed and rails returns a
200
status. However, the view from the simulator throws an error (after staying stuck on the loading screen for a few seconds). Clicking the retry button actually loads the page (cf. screenshots 1 & 2).For example, in the index page below, clicking on the main link (i.e. "MRH-L de Dora Holder") will trigger the error, but clicking on the ellipsis dropdown and on the "informations" dropdown item will load the page properly. But those two links point to the same exact URI. They alse have no
"data-turbo"="false"
attribute and nodata-turbo-action
attribute either because I want to advance (actually adding the"data-turbo-action=advance"
instead of implying it doesn't work either).The structure of this page is the following
turbo_frame
with asrc
attribute pointing to the show pageturbo_frame
pointing to the object show page as well.I don't know if this structure could have an impact on my issue.
I also made sure that my JS console doesn't throw errors on those specific pages that don't load. Once again, they work fine in other contexts (web browsers, safari) and after clicking the retry button as well. It really seems like the advance redirection mechanism, and probably the configuration of my app, are causing the issue.
Most links advance or replace, work fine. Only a few actually throw this error. And this will happen even if I don't change anything to the boilerplace (except the
local
variable in Demo.swift). But I can't figure out the pattern that will throw the error.Any help would be greatly appreciated!
Thanks,
The text was updated successfully, but these errors were encountered: