clojure-uk

thomas 2025-10-24T06:49:56.575619Z

Morning

seancorfield 2025-10-24T15:36:32.169669Z

Mornin'... Anyone use React Native and have suggestions for debugging a JS error that doesn't seem to show up in local testing? 😞

seancorfield 2025-10-28T13:10:29.586229Z

I did eventually get this all working -- with a lot of help from Copilot/Claude -- but it all came down to this: • In order to satisfy Google's latest app requirement -- 16 KB page size -- I needed to update Expo... • ...which meant I needed to update React Native... • ...which meant I needed to update React Native IAP from v12 to v14... • ...which has pretty much a completely different API for talking to Google (or Apple)... • ...and we had IAP mocked in our tests so we didn't see any breakages there 😞 • ...Copilot figured out the different API calls but our RN app passes the result of those calls directly to our wrapped web app... • ...so I had to preserve that data format (for now) by introducing v14 -> v12 convertors for products and purchases we get back from IAP... • ...and the docs suck, so ended up reading the TypeScript source files for different versions in GitHub 🤯 Wherefore art thou, backward compatibility???

thomas 2025-10-28T13:56:11.790759Z

yup, that sucks... one of the reasons I like clj that usually just works. I have had similar problems with updating Node.js version.

thomas 2025-10-27T08:15:28.469439Z

I had RN problems like this in the past. One thing that helped was getting the specific (as possible) device and then connect to that. hope that helps.

seancorfield 2025-10-27T14:13:23.453939Z

Yeah, I have a Samsung S25 with Android 16m but can't figure out how to see JS errors there, and since this relates to IAP, I can't use the emulator to debug it 😞