Skip to content

Conversation

@yuliadub
Copy link
Collaborator

@yuliadub yuliadub commented Aug 11, 2025

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

@yuliadub
Copy link
Collaborator Author

looks like CI is unhappy, looking into it

@stevekuznetsov
Copy link
Collaborator

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 :|

@yuliadub
Copy link
Collaborator Author

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

@yuliadub yuliadub force-pushed the updateExpo branch 2 times, most recently from 9b71b16 to f8561b0 Compare August 14, 2025 04:20
@yuliadub
Copy link
Collaborator Author

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

@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

@stevekuznetsov
Copy link
Collaborator

The 16k LoC diff is from running the Expo upgrade? Yikes

@yuliadub
Copy link
Collaborator Author

The 16k LoC diff is from running the Expo upgrade? Yikes

yup agreed 😨

npx expo install expo@latest npx expo install --fix

@yuliadub
Copy link
Collaborator Author

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!

@yuliadub
Copy link
Collaborator Author

expo /preview

@github-actions
Copy link

github-actions bot commented Aug 20, 2025

Preview in Expo Go

iOS Android
qrcode qrcode
exp://u.expo.dev/update/969c1fbb-710a-408d-8af5-33fda02ed546 exp://u.expo.dev/update/8f95a485-f9e4-4dd8-acd5-1ecdfa2bf6dd

@github-actions
Copy link

expo_preview: succeeded ✅
https://github.com/NWACus/avy/actions/runs/17089453536

@yuliadub
Copy link
Collaborator Author

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 😄 )

@kevinherdez
Copy link
Collaborator

kevinherdez commented Aug 21, 2025

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 😄 )

Was that testing on iPhone or Android? I tested on iPhone real quick and I hit weird issues where random zones would disappear when clicking on other ones. I'll see if I can't get them to load locally to help investigate.

IMG_0605

@stevekuznetsov
Copy link
Collaborator

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.

@stevekuznetsov
Copy link
Collaborator

xref: 8f4cce2

@yuliadub
Copy link
Collaborator Author

yuliadub commented Aug 22, 2025

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.

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 :)

@yuliadub
Copy link
Collaborator Author

expo /preview

@github-actions
Copy link

expo_preview: succeeded ✅
https://github.com/NWACus/avy/actions/runs/17146891749

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};
Copy link
Collaborator Author

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

@stevekuznetsov
Copy link
Collaborator

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.

@kevinherdez
Copy link
Collaborator

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.

Ah yeah I had forgot that you mentioned that awhile ago. Good callout

@kevinherdez
Copy link
Collaborator

kevinherdez commented Aug 22, 2025

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.

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 :)

I dug into this, and it seems like the behavior with the custom header and using absolute positioning for the views that are being shown changed. What's going on is that all of the views that use NavigationHeader and have a style set to absolute are being hidden by the header because they're no longer respecting the space being taken up by it.

Here's what I did to fix:

ObservationsScreen.tsx: remove line 69 that has ...StyleSheet.absoluteFillObject,
WeatherScreen.tsx: lines 38, 51, 62 replace style={{...StyleSheet.absoluteFillObject}} with flex={1}

A better fix for the WeatherScreen.tsx would be to create a custom StyleSheet like in ObservationsScreen to only have to change this code in one area, but hopefully are the minimum changes needed to get this fixed.

@yuliadub
Copy link
Collaborator Author

flex={1}

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!

@yuliadub yuliadub added this pull request to the merge queue Aug 29, 2025
Merged via the queue into main with commit 41ce487 Aug 29, 2025
4 of 5 checks passed
@yuliadub yuliadub deleted the updateExpo branch August 29, 2025 04:21
yuliadub added a commit that referenced this pull request Oct 18, 2025
github-merge-queue bot pushed a commit that referenced this pull request Oct 18, 2025
…ive architecture (#971)

* Revert "A few more udpates to support expo 53 SDK (#967)"

This reverts commit 805d059.

* Revert "package.json: bump to Expo 53.0.20 (#955)"

This reverts commit 41ce487.
yuliadub added a commit that referenced this pull request Nov 13, 2025
* 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
yuliadub added a commit that referenced this pull request Nov 13, 2025
…ive architecture (#971)

* Revert "A few more udpates to support expo 53 SDK (#967)"

This reverts commit 805d059.

* Revert "package.json: bump to Expo 53.0.20 (#955)"

This reverts commit 41ce487.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants