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
Hello!
I'm using FullPage.js within a next.js mobile webpage.
We are implementing dynamic routes using getServerSideProps from next.js.
If we test it locallhost, the Chrome app and Safari come out well. However,
when we apply it to a real server, the full page does not work properly.
Could you please check if any issues in my code potentially cause a problem when applied to the real server?
Android works fine. Also iPhone 12 Mini 12 works. But for 13 Pro Max and 13, both Safari and Chrome do not seem to work.
Would it be the case where allowing cross-website tracking causes a problem in the app settings?
And in the case of the iPhone, there is an issue where animation is cut off when scrolling in Chrome. Is there a way to fix it?
Can you provide an isolated reproduction of your issue in codesandbox where we can reproduce the issue?
The link you provided works as expected for me.
Hello!
I'm using FullPage.js within a next.js mobile webpage.
We are implementing dynamic routes using getServerSideProps from next.js.
If we test it locallhost, the Chrome app and Safari come out well. However,
when we apply it to a real server, the full page does not work properly.
Could you please check if any issues in my code potentially cause a problem when applied to the real server?
Android works fine. Also iPhone 12 Mini 12 works. But for 13 Pro Max and 13, both Safari and Chrome do not seem to work.
Would it be the case where allowing cross-website tracking causes a problem in the app settings?
And in the case of the iPhone, there is an issue where animation is cut off when scrolling in Chrome. Is there a way to fix it?
code:
https://codesandbox.io/p/sandbox/nervous-wildflower-bi4vow?file=%2Fpages%2Findex.tsx&selection=%5B%7B%22endColumn%22%3A1%2C%22endLineNumber%22%3A11%2C%22startColumn%22%3A1%2C%22startLineNumber%22%3A11%7D%5D
The text was updated successfully, but these errors were encountered: