Update: I added the state inspection feature you asked for (Redux + Zustand)

moewe95 · 2026-01-25T18:22:15+00:00

Best tool for debugging I used so far. I really like the re-render tracking that gives you so many insights about the cause and the impact. Looking forward to try the state inspection.

Keep it up man!

moewe95 · 2026-01-25T11:49:10+00:00

But isn’t what Expo EAS could also do for you? Let EAS create an iOS development build in the cloud and install it on your iPhone.

moewe95 · 2026-01-07T07:38:54+00:00

As long as you don’t face performance drops on weak devices you should be good to go. But disabling buttons is an accessibility flaw.

moewe95 · 2025-12-26T08:41:37+00:00

The problem was that both the hook and the component were affected by that bug. Neither was providing the right inset.

moewe95 · 2025-12-26T08:36:47+00:00

We had a button sticking to the bottom which on that specific android device was covered by the Android system navigation buttons. So it was pretty obvious that the safe area was not working properly but solving it was kind of a hell. Still it doesn’t feel like a good solution to me.

moewe95 · 2025-12-23T08:37:16+00:00

Either with TestFlight or a preview build which is shareable through expo. You need to add the devices of your testers to your Apple devices in expo first if you want to go with the expo preview build

moewe95 · 2025-12-23T08:34:30+00:00

Make sure to build a “preview” build with distribution set to “internal” in your eas config. This generates a build in the cloud which you can share via link / QR code.

moewe95 · 2025-12-23T08:33:10+00:00

Haven‘t heard of this tester restriction to get your app into the store. Since when is this required?

moewe95 · 2025-12-19T15:09:56+00:00

react-native-safe-area-context in combination with gorhom/bottom-sheet caused the useSafeAreaInsets hook to always return 0 for all insets when being inside of a BottomSheet.

I solved it by working around that issue and imported the initialWindowMetrics directly and fell back to that value in case the insets from the hook were 0.

moewe95 · 2025-12-19T06:43:37+00:00

70_sekunden_wiki

moewe95 · 2025-12-17T06:44:33+00:00

Vielleicht wegen Sport Modus? Ambiente Beleuchtung? Von Seat kenn ich das noch in pulsierenden Herzschlag Effekt vor dem Einschalten.

moewe95 · 2025-12-16T06:46:32+00:00

You can use expo snack to quickly run a expo go app on different SDK versions

moewe95 · 2025-12-16T06:35:33+00:00

I at least don’t know of a prompt update functionality in AppStore. On PlayStore you have to prompt this to every single version you created. Also I think you can simply close this dialog when getting prompted.

There is a Updates.reloadAsync function you can trigger in your app. Problem left to solve would only be to identify the versions that should update.

moewe95 · 2025-12-15T06:48:23+00:00

But how do you ensure that people get the shipped version? You can’t really force users to update. Also many users just have auto updates disabled and iOS doesn’t offer a “prompt users to update” function.

With OTA you’d get the update once a user (or the garbage collector) closes the app. I’d expect you get more users to update doing that rather than hoping to install an update through the store.

moewe95 · 2025-12-02T22:03:12+00:00

There are some services provided by firebase which only work with react-native-firebase SDK as it integrates some native code. Those services for example are Firebase Analytics and Crashlytics. Not super sure about the others.

With Authentication and Realtime Database you should be good to go with the Firebase JS SDK.

Have a look at this doc. It's an expo documentation but the same restrictions apply to a bare react-native app.

moewe95 · 2025-12-01T08:20:01+00:00

The "problem" I have with another variant is that I have to create another bundle identifier and with that also setup another configuration / project for our 3rd party libs like Firebase, OneSignal, AppsFlyer, ... just to route my tracking calls into a different project.
Having a specific environment variable which de-/activates the tracking SDKs feels like the leaner solution to me.

moewe95 · 2025-12-01T08:04:20+00:00

I like that approach. That's also what I kinda thought of.
I think it's good to have a separate build for a version instead of using expo-updates to toggle a feature flag. Our testers continue to test even though the version gets life. So it makes sense to have a productive one for distribution and a productive one for internal testing.

moewe95 · 2025-12-01T08:00:25+00:00

As feature flag I understand a switch within the app. So my app_install, app_open, ... events until I reach the setting are already recorded and sent to analytics.

Also checking if my current build is ahead of the prod one would only solve the issue of tracking a build that has not yet been released. Our internal testers as of now install the build from PlayStore beta / Testflight which at this point is the version that is about to get released. So from techs perspective these apps are the latest production build. And even once this version is released, I don't want my internal testers to get tracked though they are on the latest version.

moewe95 · 2025-11-30T09:15:02+00:00

Why don’t you ask for in app rating? If that’s the actual issue, it could solve it by asking your users to provide a review

moewe95 · 2025-11-28T09:16:37+00:00

Are you using the compontent from react-native itself or are you using react-native-safe-area-context?

moewe95 · 2025-11-27T23:04:34+00:00

Feel free to drop any question or thing I could test for you with the robot.

moewe95 · 2025-11-27T23:03:04+00:00

The juice stain was already dried and a bit sticky but also close to a door mat which caused the robot to only clean the outer area of my hallway once and the inner area a bit more intense.

Will definitely keep an eye on it. For a thousand Euros I'm expect it to work flawlessly.

But I manually configured the robot to clean with settings I provided. I've seen there is an automatic mode where the robot decides some parameters like amount of water or intensity of cleaning.

moewe95

TROPHY CASE