App won't load after upgrading to RN 0.62 - react-native

After upgrading to RN 0.62.2 from 0.61.3 using the RN tools for upgrading, updating pod (even had to modify a line in podspec following this to make it work : CocoaPods could not find compatible versions for pod "ReactCommon/jscallinvoker":)
My app build but get stuck on the splashscreen. It's working well on RN 0.61.3
This is what i have in the metro console :
[Wed Apr 22 2020 18:22:25.108] WARN Require cycle: node_modules/react-native-af-video-player/components/index.js -> node_modules/react-native-af-video-player/components/TopBar.js -> node_modules/react-native-af-video-player/components/index.js
Require cycles are allowed, but can result in uninitialized values. Consider refactoring to remove the need for a cycle.
[Wed Apr 22 2020 18:22:25.108] LOG Unable to symbolicate stack trace: Unable to resolve data for blob: (null)
[Wed Apr 22 2020 18:22:25.109] LOG Running "gamefare" with {"rootTag":151,"initialProps":{}}
[Wed Apr 22 2020 18:22:25.122] LOG Unable to symbolicate stack trace: Unable to resolve data for blob: (null)
Anyone running in the same issue and any idea on how i can debug that ?
I tried deleting node modules and reinstall everything it does not solve the problem.
When i console log from my index.js i have nothing.
EDIT : This is the full error i have in Xcode :
2020-04-24 16:46:00.478 [error][tid:com.facebook.react.JavaScript] TypeError: Object is not a constructor (evaluating 'new _reactNative.TextInput()')
2020-04-24 16:46:00.481 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: TypeError: Object is not a constructor (evaluating 'new _reactNative.TextInput()')
2020-04-24 16:46:00.490 [info][tid:com.facebook.react.JavaScript] Running "gamefare" with {"rootTag":1,"initialProps":{}}
2020-04-24 16:46:00.490 [error][tid:com.facebook.react.JavaScript] Invariant Violation: "gamefare" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.
2020-04-24 16:46:00.498 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: Invariant Violation: "myAppName" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.
2020-04-24 16:46:00.594 [info][tid:com.facebook.react.JavaScript] Unable to symbolicate stack trace: Unable to resolve data for blob: (null)
2020-04-24 16:46:00.604 [info][tid:com.facebook.react.JavaScript] Unable to symbolicate stack trace: Unable to resolve data for blob: (null)

Finally after some search, i had to disable page per page all my component to see what was the cause of the problem. It appear that this package i was using : react-native-confirmation-code-fieldneeded to be updated ! (the maintainer was aware of the problem with RN 0.62 and updated it, thanks to him !
I also needed to update reac-native-firebase if someone run into the same problem and use those modules.
The best way to debug is to do bit by bit by removing everything and added all the piece back together component per component when log in console are not clear

Related

Unable to get the source file of an error on react-native

I am debugging an application that throws me the error of
ERROR Error: Invalid hook call. Hooks can only be called inside of the body of a
function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See react-invalid-hook-call for tips about how to debug and fix this problem.
[Fri Oct 23 2020 09:04:14.325] ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
But it doesn't say where is the source file of the error... since it is a big application I am having trouble finding where this error is located.
I am able to compile the application but the error happens on the initialization.
When I run the debugger it says the following on the developers console...
Unable to symbolicate stack trace: The stack is null
Plus the previous errors.
Any idea how I could locate the source file of this errors?
Thank you for your help!

Internal server error when trying to build and deploy to AEM

My local AEM instance suddenly stopped working when I switched branches in git and installed the package with
mvn clean install -PautoInstallPackage.
The build failed with [ERROR] Request to http://localhost:4502/crx/packmgr/service.jsp failed, response=Internal Server Error
My error log shows the following errors:
25.10.2018 11:52:33.607 *ERROR* [127.0.0.1 [1540504353564] POST /crx/packmgr/service.jsp HTTP/1.1] org.apache.jackrabbit.oak.spi.security.authentication.external.impl.ExternalLoginModule No IDP found with name 0654f74c177ec80b60f7922a9a6195cf. Will not be used for login.
25.10.2018 11:52:33.607 *ERROR* [127.0.0.1 [1540504353564] POST /crx/packmgr/service.jsp HTTP/1.1] org.apache.jackrabbit.oak.spi.security.authentication.external.impl.ExternalLoginModule No IDP found with name a9dea3b044e912071cbffd4839016d2e. Will not be used for login.
25.10.2018 12:00:30.005 *INFO* [sling-default-2-Registered Service.1079] com.adobe.granite.taskmanagement.impl.jcr.TaskArchiveService archiving tasks at: 'Thu Oct 25 12:00:30 HST 2018'
25.10.2018 12:00:58.610 *ERROR* [127.0.0.1 [1540504858546] POST /crx/packmgr/service.jsp HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
java.io.IOException: Unable to get component of class 'interface org.apache.sling.rewriter.Generator' with type 'htmlparser'.
I've tried adding <useProxy>false</useProxy> to my parent POM file as suggested on a similar thread posted here but that also did not work. I've tried recloning the repo and starting over but since it's a server error that did nothing.
Additional Info:
Running on Windows 10
AEM 6.4
Any assistance will be greatly appreciated.
Thanks!
Thanks for your help. The issue actually happened when I switched branches and installed and deployed the package over the existing package in AEM. By removing the quickstart folder and restarting the JAR file, thus creating a new AEM directory, I was able to install and deploy the correct branch without error.

Aurelia - Karma error

I am following the Aurelia docs for Production setup and I am encountering an issue with the the Running The Unit Tests section.
I have the app running with no issues. I open a new terminal window and successfully installed karma-cli 3.9.3. But when I run gulp test I get the following error:
31 05 2016 15:58:09.929:INFO [Chrome 51.0.2704 (Mac OS X 10.11.5)]: Connected on socket /#kJiah_Vi_OxBaoMGAAAA with id 68824261
Chrome 51.0.2704 (Mac OS X 10.11.5) ERROR
Uncaught TypeError: Cannot read property 'config' of undefined
at /Users/XXX/Documents/Websites/Aurelia/Production/node_modules/karma-jspm/src/adapter.js:18
I know enough that I should not be editing any source files in node_modules, so how do I go about fixing this?

Appcelerator Doesnt Accept Developer Certificate

Appcelerator made me crazy!!!
I'm trying to compile / test / build etc. but I stuck with the error below. First I thought it happened because I updated to El Capitan and gives these errors only for iOS builds.
Later,
I realized It happens when I try to build for Android on Windows.
Please help me guys,
I have done lots of things but I couldn't get solved this!
Logging out doesn't solved anything. Certificates also changed nothing. (On OS X)
Is it related with my account type on appcelerator platform or anything otherwise that I couldn't understand...
[ERROR] : Developer Certificate Invalid. Please logout using `appc logout -D` and then re-login again.
2015-12-03T18:42:18.785Z | TRACE | titanium exited with exit code 100
2015-12-03T18:42:18.786Z | ERROR | Error: ti run exited with error code 100
at ChildProcess.<anonymous> (C:\Users\Mustafa\.appcelerator\install\5.1.0\package\node_modules\appc-cli-titanium\plugins\run.js:92:66)
at ChildProcess.emit (events.js:110:17)
at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
2015-12-03T18:42:18.787Z | TRACE | Sending exit signal to titanium process: 3372
[ERROR] Application Installer abnormal process termination. Process exit value was 1
In my case this error was caused by non-english character used in my surname. I'd suggest you login to Appcelerator's dashboard and verify your account's details (first name, last name).

Build Failed - validate build/release

Just a few days ago I could both run (in the simulator and on my iphone device) and package my iOS app for the iOS iTunes Store. But now I cannot get past this error during package:
[ERROR] : ** BUILD FAILED **
[ERROR] : The following build commands failed:
[ERROR] : Validate build/Release-iphoneos/Trivia\ Rain.app
[ERROR] : (1 failure)
TRACE | titanium exited with exit code 1
ERROR | Error: ti run exited with error code 1
at ChildProcess.<anonymous> (/Users/natej/.appcelerator/install/4.1.2/package/node_modules/appc-cli-titanium/plugins/run.js:84:66)
at ChildProcess.emit (events.js:117:20)
at Process.ChildProcess._handle.onexit (child_process.js:810:12)
Since a few days ago when the package worked perfectly, I have changed nothing related to my keychains, keystore, profiles, certificates, etc. I have made a few code changes, but after my changes, the app compiled fine, runs in simulator, and deploys/runs on my iphone 6 device. I have double checked that my certs and distribution profiles are all valid, and nothing has changed from a few days ago.
I have cleaned my project, restarted Appcelerator Studio, restarted my mac. Still I cannot get past this error.
Any ideas?
I came back 4 days later after having these problems, having changed nothing (no code, no settings, no Appcelerator updates)...and it simply worked this time.
In summary, Appcelerator is buggy. :-|