Closed kr-yeon closed 3 months ago
[super. bridge reload]; Occurs when running code
I have this same issue. I've found that the CodePush gets applied most of the time, but requires the user to re-open the app after it crashes. Happens more on Android than iOS for me, but still occasionally on iOS.
I use react-native-code-push version: 8.0.2. I have the same issue, iOS happens more than Android. Is it because Code push currently only supports 0.71 and not yet 0.71.6?
I use react-native-code-push version: 8.0.2. I have the same issue, iOS happens more than Android. Is it because Code push currently only supports 0.71 and not yet 0.71.6?
I am currently using rn 0.71.11 I updated once but still have the same problem
I have exactly the same problem. at first i suspected reanimated, but after patching it, i still get the bug.
Only in "release", according to sentry tracking, it's a RAM problem:
WatchdogTermination: The OS watchdog terminated your app, possibly because it overused RAM.
I try to replace code-push with react-native-restart and I have the same issue, also reported by other here
I use react-native v0.71.1
reanimated patch for react-native-reanimated 3.1.0
=>
diff --git a/node_modules/react-native-reanimated/ios/LayoutReanimation/REAAnimationsManager.m b/node_modules/react-native-reanimated/ios/LayoutReanimation/REAAnimationsManager.m
index 365ae4f..6290823 100644
--- a/node_modules/react-native-reanimated/ios/LayoutReanimation/REAAnimationsManager.m
+++ b/node_modules/react-native-reanimated/ios/LayoutReanimation/REAAnimationsManager.m
@@ -396,7 +396,7 @@ BOOL REANodeFind(id<RCTComponent> view, int (^block)(id<RCTComponent>))
return NO;
}
- BOOL hasExitAnimation = _hasAnimationForTag(view.reactTag, EXITING) || [_exitingViews objectForKey:view.reactTag];
+ BOOL hasExitAnimation = [self hasAnimationForTag:view.reactTag type:EXITING] || [_exitingViews objectForKey:view.reactTag];
BOOL hasAnimatedChildren = NO;
shouldRemoveSubviewsWithoutAnimations = shouldRemoveSubviewsWithoutAnimations && !hasExitAnimation;
NSMutableArray *toBeRemoved = [[NSMutableArray alloc] init];
@@ -521,7 +521,7 @@ BOOL REANodeFind(id<RCTComponent> view, int (^block)(id<RCTComponent>))
{
LayoutAnimationType type = before == nil ? ENTERING : LAYOUT;
NSNumber *viewTag = view.reactTag;
- if (_hasAnimationForTag(viewTag, type)) {
+ if ([self hasAnimationForTag:viewTag type:type]) {
REASnapshot *after = [[REASnapshot alloc] init:view];
if (before == nil) {
[self onViewCreate:view after:after];
@@ -533,7 +533,7 @@ BOOL REANodeFind(id<RCTComponent> view, int (^block)(id<RCTComponent>))
[self setNewProps:before.values forView:view];
}
- if (_hasAnimationForTag(viewTag, SHARED_ELEMENT_TRANSITION)) {
+ if ([self hasAnimationForTag:viewTag type:SHARED_ELEMENT_TRANSITION]) {
if (type == ENTERING) {
[_sharedTransitionManager notifyAboutNewView:view];
} else {
diff --git a/node_modules/react-native-reanimated/src/reanimated2/mappers.ts b/node_modules/react-native-reanimated/src/reanimated2/mappers.ts
index 4e66106..bc8712f 100644
--- a/node_modules/react-native-reanimated/src/reanimated2/mappers.ts
+++ b/node_modules/react-native-reanimated/src/reanimated2/mappers.ts
@@ -80,8 +80,11 @@ export function createMapperRegistry() {
}
function mapperRun() {
- processingMappers = true;
runRequested = false;
+ if (processingMappers) {
+ return;
+ }
+ processingMappers = true;
if (mappers.size !== sortedMappers.length) {
updateMappersOrder();
}
BTW I use Xcode_14.3.1.app to build the app
@kr-yeon Does this crash happen through your local XCode with a release build?
yeah
2023년 8월 19일 (토) 오전 12:21, Anthony LASSERRE @.***>님이 작성:
@kr-yeon https://github.com/kr-yeon Does this crash happen through your local XCode with a release build?
— Reply to this email directly, view it on GitHub https://github.com/microsoft/react-native-code-push/issues/2539#issuecomment-1684074767, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRSJAEBTSIXME33J2VZGQTXV6B7LANCNFSM6AAAAAAZVO4QFY . You are receiving this because you were mentioned.Message ID: @.***>
@kr-yeon Which MacOS version are you using ?
Ventura 13.4 XCodeVersion is 14.3
2023년 8월 19일 (토) 오전 12:25, Anthony LASSERRE @.***>님이 작성:
@kr-yeon https://github.com/kr-yeon Which MacOS version are you using ?
— Reply to this email directly, view it on GitHub https://github.com/microsoft/react-native-code-push/issues/2539#issuecomment-1684079383, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRSJADGZWVDMQV6GEGHFO3XV6CNNANCNFSM6AAAAAAZVO4QFY . You are receiving this because you were mentioned.Message ID: @.***>
Should we consider react-native-code-push as deprecated?
In fact, I excluded CodePush from the project. I don't know if I'm stupid, but I couldn't find the answer.
I face the issue on Android , but work on iOS. Anyone face it on Android too?
I'm also experiencing that issue only on Android. I thought it might be a problem with the built bundle's asset path, but I removed Codepush first.
2024년 1월 20일 (토) 오후 11:54, DanLin @.***>님이 작성:
I face the issue on Android , but work on iOS. Anyone face it on Android too?
— Reply to this email directly, view it on GitHub https://github.com/microsoft/react-native-code-push/issues/2539#issuecomment-1902119799, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRSJABFPLDEDE2KE32E3PDYPPLDHAVCNFSM6AAAAAAZVO4QF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSGEYTSNZZHE . You are receiving this because you were mentioned.Message ID: @.***>
Hi everyone! Could you please confirm what this issue still persist on latest version (8.2.1)?
Any solutions, I am facing with iOS on release app. It crashes after restart
The best solution is to drop codepush and use expo
Im facing this same issue with expo-updates as well.
any changes for this?
Hi @Logan-FE thank you for reaching out. Does this issue still reproduce on latest 8.3.1 version?
Im facing this same issue with expo-updates as well.
- "react-native-reanimated": "3.6.2",
- "react-native": "0.73.4",
- "expo": "~50.0.11",
- "expo-updates": "~0.24.11",
@vlimag vlimag you found any alternative or solution with this?
@DordeDimitrijev I'm facing same problem, distribution is fine but to effect on android application
"react-native-code-push": "^8.3.1",
"react-native": "0.73.4",
@nihal-37-37 , are you using react-native-reanimated
in direct or transitive dependencies? Could you share your crash log?
Steps to Reproduce
Expected Behavior
What you expected to happen? Restart Application
Actual Behavior
What actually happens?
Shutdown app
Reproducible Demo
Examples
folder runnode create-app.js appName react-native@0.61.5 react-native-code-push@6.0.0
command to generate plain CodePushified React Native app. Please see description on top ofcreate-app.js
file content if neededEnvironment
(The more info the faster we will be able to address it!)