-
Notifications
You must be signed in to change notification settings - Fork 13
package.json: bump to Expo 53.0.20 #955
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
looks like CI is unhappy, looking into it |
|
If you can, don't blow away node_modules and re-install, it will change so many dependencies it's very hard to guarantee that we didn't regress things. In the past we've introduced a dozen bugs that way :| |
good to know! I will try again without blowing it away |
9b71b16 to
f8561b0
Compare
@stevekuznetsov ok, not blowing away yarn.lock but the changes still look massive. Wonder if that is because I am updating a lot of packages? Seems like that is good to do since we are behind on a few. There are at least 2 packages I found where the newer version will require some code refactor, I will make issue for those but right now upped them to the version that still works with code as is. still need to fix yarn test |
|
The 16k LoC diff is from running the Expo upgrade? Yikes |
yup agreed 😨
|
|
ok. to follow up on this - something weird is happening with one of my Windows machines that is running WSL. When I went to run yarn install on my different windows machine, the changes in yarn.lock look a lot more reasonable and what we would expect. Still need to figure out why the tests are failing but getting close! |
|
expo /preview |
|
expo_preview: succeeded ✅ |
|
alright, got all this resolved but now if you look at the expo go preview - when clicking into a map zone, looks like the app crashes. Gonna keep debugging whats up (the map doesnt load on the emulator on my machine so gotta get creative 😄 ) |
|
The "new architecture" breaks the map entirely - IIRC in Expo Go, they always run the new architecture, regardless of whether your project's config has it turned on or not. So, I think that's expected behavior and won't happen in the preview app. |
|
xref: 8f4cce2 |
well its actually interesting - on an android emulator inside expo go no maps loads for me period. When running expo preview here from the PR, with the app also opening in expo go, the map does load and it crashes when I go to a specific zone, so I do think this is a real crash (plus Kevin did confirm that he is seeing this on iOS as well) thanks to @kevinherdez, the map now works and the obs submit button as well (another thing that was broken by the updates) - right now something is up with the header in obs list and obs details. Filter is missing and on obs detailed page the top section is hidden under the header. my emulator refused to load the app for some reason so I didnt have the chance to dig further. If you have a chance to look and find anything, here for all the help to get this finished :) |
|
expo /preview |
|
expo_preview: succeeded ✅ |
| firstOpen = true; | ||
| // set back to not be null since we want a shared obs to have a back button | ||
| back = {title: 'Observations'}; | ||
| back = {title: 'Observations', href: undefined}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to look into what href should be
|
Sure, of course chase real breaks, but keep that in mind since you will get weird behavior with the zones, etc, and there's nothing to be done. |
Ah yeah I had forgot that you mentioned that awhile ago. Good callout |
I dug into this, and it seems like the behavior with the custom header and using Here's what I did to fix:
A better fix for the |
sweet, that did it. agree that we can refactor in the future! I think I wanna merge this PR first (#904) and then merge this. did a quick look around and didnt find any other issues, but we will also run a deeper test on the preview app once we get a preview build! |
* update expo to 53.0.20. ensure yarn.lock is not being blown away * eslint came up with more errors somehow * fix tests * making expo doctor a bit happier * more package updates to help fix crashes * fix error created by previous package update * fix cutoff headers
Updating expo and dependencies. Ran into a random error with @types/md5 module not being found but after a clean install of all packages everything booted as expected.
Did the upgrade following expo directions here: https://docs.expo.dev/workflow/upgrading-expo-sdk-walkthrough/
had to up version of node to support the upgrades in GAH setup.
had to update some eslint ignores
had to resolve some new typescript complaints