Cassie

I still can't view the issue I'm afraid and I don't have an android phone. The only advice I have, from looking at the code is to remove "scroll-behaviour: smooth" - Maybe that will p. Other than that, to use ScrollSmoother (our smooth scroll plugin) rather than locomotive scroll.

That's the one! It's a common tripping up point. I'll add some info in the installation helper. Glad we helped to get there in the end. (And yeah, thanks for the heads up! I just keep package.lock files far away from netlify if a build is failing as they're a pretty sure fire way of continuing down the exact same path)

You're testing inside an iframe which isn't advisable as the final website won't exist inside an iframe. I can't see the issue on mobile or desktop or in the iframe though. Please explain steps to reproduce e.g. - Open in mobile safari - Scroll with a trackpad to the bottom of the page a-ok.mp4

(Also thanks so much for going through this frustration - It's not in vain, when we get to the bottom of this we can make things easier for other people who may run into the same issues)

Let's just focus on one thing at a time Does the same 'shaking' issue appear for you on mobile in this demo? https://stackblitz.com/edit/stackblitz-starters-lptpdj?file=app%2Fpage.tsx

Hey - So this isn't a bug on our end. I downloaded your repo and it deployed first time. https://66ebfa071398367641375845--test-usegsap-deploy-netlify.netlify.app/ The only change I made was that I noticed you didn't have package-lock detailed in the gitignore. Is it possible that you pushed up a package lock with information about the private registry in? @gsap/react isn't registered as a paid plugin, something in *your* particular setup is directing to the wrong registry - this is usually because you've got an upstream .npmrc with the PAID GSAP registry https://npm.greensock.com<---- paid registry (the package doesn't exist here) https://registry.npmjs.org <------ correct registry (it does exist here) (You should never have to edit the package lock directly, this is a clear sign that you have something, somewhere that is setting the incorrect registry) From the thread I linked to - could you run npm config list in your terminal for me? Thanks so much!

Thanks, but this is a live site not a minimal demo. Would you please provide a very simple CodePen or Stackblitz that illustrates the issue? Please don't include your whole project. The link you've sent includes hero animations, button animation and videos. Just some colored <div> elements and the GSAP code is best. See if you can remove as much code as possible while still demonstrating the issue. Usually people solve their own issues during this process! If not, at least we have a reduced test case which greatly increases your chances of getting a relevant answer. Here's a starter CodePen that loads all the plugins. Just click "fork" at the bottom right and make your minimal demo: Using a framework/library like React, Vue, Next, etc.? CodePen isn't always ideal for these tools, so here are some Stackblitz starter templates that you can fork and import the gsap-trial NPM package for using any of the bonus plugins: React (please read this article!) Next Svelte Sveltekit Vue Nuxt Please share the StackBlitz link directly to the file in question (where you've put the GSAP code) so we don't need to hunt through all the files. Once we see an isolated demo, we'll do our best to jump in and help with your GSAP-specific questions. ✅

Hi there. We can help if you can provide a minimal demo showing the issue - not a video. We need to be able to see the code and make changes in order to help you. Also, worth noting that this is an emulated scroll and does not necessarily represent a real mobile browser. I use the responsive view for testing very basic responsive layout - not behaviour. It's best to test on real devices.

Ah this is worth a note in the install helper if this works - let us know! 👀

Hi there, You are right - It is free. The issue here is likely that your build tool is looking at the wrong registry. This usually happens if someone's got an .npmrc file referencing the club GSAP repo somewhere further up the folder tree Take a look at this thread, it might help. Let me know how you get on.

Sorry we can't offer a silver bullet advice-wise here.