Difference between revisions of "Floodzuki Expo Upgrade Notes"
| Line 46: | Line 46: | ||
The map is currently blank when running an EAS build. I originally thought that this was because of a missing environment variable | The map is currently blank when running an EAS build. I originally thought that this was because of a missing environment variable | ||
but now I am not sure. I am investigating. | but now I am not sure. I am investigating. | ||
| + | |||
| + | It appears that the Google Maps API key has to have the app's SHA1 fingerprint -- Once I resolve the dark mode issue I'll try to | ||
| + | resolve this. | ||
Revision as of 15:48, 20 September 2025
Floodzuki Expo 54 Upgrade Notes
This is an uncategorized list of notes about updating Floodzuki's Expo version to v54. This is mostly here for posterity, in the hopes that it might help with future upgrades.
Overall Notes
Directly upgrading the expo version was going to be very complicated, because there are a number of big changes:
- new react native architecture
- no more @expo/sentry package
- file-based routing issues
Because of this, my approach was to build a new empty Expo 54 project with Sentry and then take the basic framework, and all of the expo versions, into the floodzuki project.
One side effect was moving all of the components, utils, etc, out of /app and into a new /src directory. Having them in /app was causing a lot of warnings about default exports, because file-based-routing was expecting anything in /app to be a route. This change may not have been necessary, but I wanted to go ahead and do it so that if we want to use file-based routing in the future it'll be easier.
Dark Mode
Status: UNRESOLVED
Support for dark mode has changed in Expo. We want to force our app to run in light mode, because we haven't yet taken the time to make the app work correctly in dark mode (for example, the text in text fields renders white-on-white when in dark mode).
In Expo we can supposedly force the app to run in light mode only by adding ``` userInterfaceStyle: "light" ``` in various places in app.config.ts. Additionally, on Android, the package expo-system-ui is required.
Unfortunately, even with these changes, this is not yet working. We are correctly forcing light mode when run directly either on the emulator or on a real Android device, but the EAS-built preview version is still running in dark mode:
Map is blank
Status: UNRESOLVED
The map is currently blank when running an EAS build. I originally thought that this was because of a missing environment variable but now I am not sure. I am investigating.
It appears that the Google Maps API key has to have the app's SHA1 fingerprint -- Once I resolve the dark mode issue I'll try to resolve this.
