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
This doesn't seem to affect anything as far as I can tell, but I noticed this when investigating #48. In the visitProposedToLocation function, when it's a turbo frame navigation, the options object has objects (request and snapshot) and functions (visitCachedSnapshot) inside of it, which I think can't be cloned, resulting in a DataCloneError being thrown.
is the line that is affected. I noticed that you can fix it by turning it into a pure JSON object a la https://stackoverflow.com/a/68468806/90551 but I didn't notice any different behavior after doing so. Still, it makes me wonder if something is lost along the way due to this, so I thought I'd report it. I wonder if it makes sense to "clean" objects sent to postMessage somewhere, or if a more pared down options object should be passed in somewhere upstream of this function in this case.
Thanks!
To reproduce:
Set up a web app with turbo frame navigation
Open the iOS app in simulator
Connect to the app via Safari's debugging tools
You should see the error in the JS console
The text was updated successfully, but these errors were encountered:
This doesn't seem to affect anything as far as I can tell, but I noticed this when investigating #48. In the
visitProposedToLocation
function, when it's a turbo frame navigation, the options object has objects (request
andsnapshot
) and functions (visitCachedSnapshot
) inside of it, which I think can't be cloned, resulting in aDataCloneError
being thrown.hotwire-native-ios/Source/Turbo/WebView/turbo.js
Line 114 in 0bc9f80
Thanks!
To reproduce:
The text was updated successfully, but these errors were encountered: