Floodzuki Expo Upgrade Notes - Revision history

DaveSanderman: /* Floodzuki Expo 54 Upgrade Notes */

2025-10-09T15:39:22Z

Floodzuki Expo 54 Upgrade Notes

DaveSanderman: /* Dark Mode */

2025-10-02T03:39:07Z

Dark Mode

DaveSanderman: /* Dark Mode */

2025-10-01T22:06:01Z

Dark Mode

DaveSanderman: /* Map is blank */

2025-09-22T13:57:42Z

Map is blank

DaveSanderman: /* Dark Mode */

2025-09-22T13:54:27Z

Dark Mode

DaveSanderman: /* Local EAS Build */

2025-09-20T19:22:09Z

Local EAS Build

DaveSanderman: /* Dark Mode */

2025-09-20T17:04:25Z

Dark Mode

DaveSanderman: /* Map is blank */

2025-09-20T17:03:47Z

Map is blank

DaveSanderman at 16:35, 20 September 2025

2025-09-20T16:35:55Z

DaveSanderman: /* Map is blank */

2025-09-20T15:48:37Z

Map is blank

← Older revision		Revision as of 15:39, 9 October 2025
Line 38:		Line 38:

	NOTE! This can sometimes just fail, and immediately re-running it might succeed. Yay!		NOTE! This can sometimes just fail, and immediately re-running it might succeed. Yay!
		+
		+	=== Testing Production Android Build ===
		+
		+	The output of the production Android build is an .AAB file. You can test this via the Play store by doing
		+	an "Internal App Sharing" build. You can set it so that anybody who gets the link can install it, but they
		+	must first follow the instructions at [[https://support.google.com/googleplay/android-developer/answer/9844679?hl=en&visit_id=638956146134832092-1454217124&rd=1#zippy=%2Cupload-and-share-apps-for-testing this page]] under "How authorized testers turn on internal app sharing."

	=== Dark Mode ===		=== Dark Mode ===

@@ Line 41: / Line 41: @@
 === Dark Mode ===
-Status: BROKEN
+Status: Fixed
 Support for dark mode has changed in Expo.  We want to force our app to run in light mode, because we haven't
@@ Line 54: / Line 54: @@
 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
+This is not enough (and I don't really know if it's necessary).  As of Expo 54, various packages set up the default
-directly either on the emulator or on a real Android device, but the EAS-built preview version is still running
+Android theme to be based on Theme.AppCompat.DayNight.NoActionBar, which allows dark mode for the app no matter what
-in dark mode:
+other settings are done.  I've added a plugin (plugins/withForceLightModeThemeAndroid.js) that explicitly forces
+the theme to be based on light mode.  To verify this, do a local EAS build and look at
-[[File:Dark-mode-footer.png]]
+<pre>
+build/android/app/src/main/res/values/styles.xml:
-UPDATE: I've been able to finally get an EAS local build working, and the problem appears there also, so I should
+<resources xmlns:tools="http://schemas.android.com/tools">
-be able to examine the build processes and see what's different.
+  <style name="AppTheme" parent="Theme.AppCompat.Light.NoActionBar">
+    <item name="android:enforceNavigationBarContrast" tools:targetApi="29">true</item>
-UPDATE: Not sure why but this seems to be actually working now? I added expo-system-ui to plugins, and experimented
+    <item name="android:editTextBackground">@drawable/rn_edit_text_material</item>
-with explicitly setting the app background color to verify that it was getting imported/loaded, and now the app is
+    <item name="colorPrimary">@color/colorPrimary</item>
-forcing light mode correctly.
+    <item name="android:statusBarColor">#ffffff</item>
-UPDATE: As of the latest build, the problem is back.
+The fixed version has Theme.AppCompat.Light.NoActionBar instead of Theme.AppCompat.DayNight.NoActionBar.
 === Map is blank ===

@@ Line 41: / Line 41: @@
 === Dark Mode ===
-Status: resolved?
+Status: BROKEN
 Support for dark mode has changed in Expo.  We want to force our app to run in light mode, because we haven't
@@ Line 66: / Line 66: @@
 with explicitly setting the app background color to verify that it was getting imported/loaded, and now the app is
 forcing light mode correctly.
 === Map is blank ===

@@ Line 69: / Line 69: @@
 === Map is blank ===
-Status: UNRESOLVED
+Status: Resolved
 The map is currently blank when running an EAS build.  I originally thought that this was because of a missing environment variable
@@ Line 80: / Line 80: @@
 figure out what the right full solution is for this, but it may just be: don't restrict the development-mode key, and just make
 sure that it isn't ever used in production.

@@ Line 41: / Line 41: @@
 === Dark Mode ===
-Status: UNRESOLVED
+Status: resolved?
 Support for dark mode has changed in Expo.  We want to force our app to run in light mode, because we haven't
@@ Line 62: / Line 62: @@
 UPDATE: I've been able to finally get an EAS local build working, and the problem appears there also, so I should
 be able to examine the build processes and see what's different.
 === Map is blank ===

@@ Line 36: / Line 36: @@
 eas build --profile preview --platform android --local
 </pre>
 === Dark Mode ===

← Older revision		Revision as of 17:04, 20 September 2025
Line 57:		Line 57:

	[[File:Dark-mode-footer.png]]		[[File:Dark-mode-footer.png]]
		+
		+	UPDATE: I've been able to finally get an EAS local build working, and the problem appears there also, so I should
		+	be able to examine the build processes and see what's different.

	=== Map is blank ===		=== Map is blank ===

← Older revision		Revision as of 17:03, 20 September 2025
Line 67:		Line 67:
	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		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.		resolve this.
		+
		+	UPDATE: Removing the fingerprint limitation on the development-mode API key resolves the issue; I'll continue investigating to
		+	figure out what the right full solution is for this, but it may just be: don't restrict the development-mode key, and just make
		+	sure that it isn't ever used in production.

@@ Line 19: / Line 19: @@
 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 ===
@@ Line 29: / Line 46: @@
 In Expo we can supposedly force the app to run in light mode only by adding
-```
+<pre>
 userInterfaceStyle: "light"
-```
+</pre>
 in various places in app.config.ts.  Additionally, on Android, the package expo-system-ui is required.

← Older revision		Revision as of 15:48, 20 September 2025
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.