@shakenbake/react-native 0.0.9 → 0.0.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +30 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -121,6 +121,36 @@ On simulators, shake gestures can conflict with the development menu. Disable th
|
|
|
121
121
|
|
|
122
122
|
This keeps physical devices working normally while avoiding simulator `NativeEventEmitter` issues.
|
|
123
123
|
|
|
124
|
+
### Runtime detection behavior
|
|
125
|
+
|
|
126
|
+
The SDK now performs runtime checks around `react-native-shake`:
|
|
127
|
+
|
|
128
|
+
- If native `RNShake` is unavailable, shake activation is skipped (no crash).
|
|
129
|
+
- If `react-native-shake` throws `NativeEventEmitter` errors in the current runtime, shake activation is skipped.
|
|
130
|
+
- If `config.enableShakeTrigger === false`, the built-in shake trigger is not registered.
|
|
131
|
+
|
|
132
|
+
You may see logs such as:
|
|
133
|
+
|
|
134
|
+
- `[ShakeNbake] iOS dev runtime detected; shake trigger disabled (use manual trigger)`
|
|
135
|
+
- `[ShakeTrigger] Native RNShake module not found; shake trigger disabled for this runtime`
|
|
136
|
+
|
|
137
|
+
These are expected in simulator/dev flows when shake is disabled or unsupported.
|
|
138
|
+
|
|
139
|
+
### If you still see NativeEventEmitter errors after upgrading
|
|
140
|
+
|
|
141
|
+
Your app is likely running a stale mixed `node_modules` state. Reset and reinstall:
|
|
142
|
+
|
|
143
|
+
```bash
|
|
144
|
+
rm -rf node_modules
|
|
145
|
+
yarn install
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
Then restart Metro with cache clear:
|
|
149
|
+
|
|
150
|
+
```bash
|
|
151
|
+
npx expo start --dev-client -c
|
|
152
|
+
```
|
|
153
|
+
|
|
124
154
|
### Android GL/Skia screenshot capture
|
|
125
155
|
|
|
126
156
|
On Android, `react-native-view-shot` may produce blank or incomplete screenshots when GL-rendered surfaces (Skia, MapView, camera previews) are present. The SDK automatically enables `handleGLSurfaceViewOnAndroid` on Android to ensure these surfaces are captured correctly. No manual configuration is needed.
|