keyboard-manager | Small keyboard shortcut management | Keyboard library

Some of the changes to get the build working, from comments:

From your package.json, your cli version is at ^2.0.1 and 2.0.1 is indeed the version of the cli that had the issue you linked to from github.com/facebook/react-native/issues/25479 Have you verified that the line similar to def command = "../node_modules/.bin/react-native config" (from github.com/facebook/react-native/issues/…) in your node_modules/@react-native-community/cli-platform-android/native_modules.gradle is correct? You should also ensure your installed version of the cli is >= 2.0.2.

Make sure your buildTypes and productFlavors definitions in android/app/build.gradle are set up to include all the different variants you are trying to build in your jenkins job. Looks like you have flavors for dev, qa, ua and prod. Check out the gradle docs developer.android.com/studio/build/build-variants#build-types for more info.

Looks like you're missing a getAppName function in your build.gradle. Something like ext.getAppName = {suffix = '' -> 'MyAppName' + suffix}. A quick scan of your build.gradle looks like you need another called getLauncher which returns an appropriate string for whatever you use link_launcher for.

At some point I introduced what I can only guess were dependency bugs when I attempted to upgrade is my guess. I had a snapshot of a working application with version 0.53.3 that I had set aside.

I was having problems with that one too until a colleague suggested I upgrade Detox version from 8.x.x to 12.0.0 because it was not playing nice with Xcode 10.1.

I did so and the app was no longer crashing.

I was able to access the MacOS logs by going to spotlight and typing in console, clearing out the console and then observing it as I attempted to open the app within the simulator.

There will be a lot to look over as with most logs, but the error message that is a good starting point:

Terminating app due to uncaught exception 'RCTFatalException: Unhandled JS Exception: Cannot create styled-component for component: [object Object]', reason: 'Unhandled JS Exception: Cannot create styled-component for component: [object Object]

Okay so after I removed Metro version 29, I just kept running these commands repeatedly:

rm -rf node_modules && npm install && npm run setup && react-native run-ios

and now it boots past the splash screen with yet another, but more familiar error.

There were actually two separate issues going on here. The

WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED

error had to do with the fact that port 8081 was already in use so I had to kill all processes completely.

Definitely some dependency issues going on between Babel and one or two custom packages, which was primary react-native-keyboard-manager and react-native-input-scroll-view. I removed these and used react-native's ScrollView instead.

I was then able to successfully run:

react-native bundle --entry-file ./index.js --platform ios --bundle-output ios/main.jsbundle --verbose

That was able to successfully create the main.jsbundle, but unfortunately that was not the root cause of the app crashing as it is still crashing and doing so silently now.

What resolved this error was by removing the Instabug library and code from App.js file:

You need to import your reactotron configuration file in: - App.js (if your project was created using Create React Native App) or - index.js on line 1:

import 'pathtofile/ReactotronConfig.js';

you can also take a look at this link for start guide. https://github.com/infinitered/reactotron/blob/master/docs/quick-start-react-native.md

i created a project from scratch and it did work for me it seems that the problem is the version of this two packages, try updating them from:

"reactotron-react-native": "1.14.0",

"reactotron-redux": "1.13.0"

to:

"reactotron-react-native": "^3.5.0",

"reactotron-redux": "^3.1.0"

The issue was with an import statement in one of the action.js files.

Instead of import types from './constants'; like the rest of the types files or constant files, it had import types from './types';

After I corrected that, the index.ios.js build was succeeding again.

My app also got rejected. However after replying in the resolution centre I have said that I do not use code obfuscating and I have asked for details about the reason for rejection. And just like that, I've got a notification that my app is in review and like 10 seconds later my app was approved and released :-)

To me this seems like either a bug on Apple side, or it was triggered by one of the popular frameworks, like AFNetworking, Realm, etc (where they use NSStringFromSelector, NSStringFromClass etc) but since it was large scale and everyone was explaining the usage in the same way the apps gets approved almost automatically (but you have to reply in the resolution centre in order to trigger the second review process). Hope this helps.