iOS app won't load if react-native-openpgp is imported and remote debugger is enabled

[davidjb]

After attempting to import this module like so:

import * as openpgp from 'react-native-openpgp'

and running react-native run-ios with Remote JS Debugging enabled, my iOS app doesn't load, specifically not proceeding past the following screen:

Dev tools in Chrome launches automatically and connects successfully, but the app screen remains at Loading from localhost:8081. It's just the import line that triggers the issue, because if I go ahead and comment out the import line, the app loads fine. Similarly, if debugging isn't enabled, the app loads fine and the OpenPGP code works correctly.

If I go ahead and shutdown the packager and restart it, the very first reload of the running app will start transforming/loading modules, but the app won't finish loading. This is the output on the console from react-native start --verbose:

Looking for JS files in
   /Users/david/dev/App

Loading dependency graph...
React packager ready.

Loading dependency graph, done.
Bundling `index.ios.js`
  Transforming modules  99.1% (1603/1610), done.
Bundling `index.ios.js`
  No module changed.
Bundling `index.ios.js`
  No module changed.
Bundling `index.ios.js`
  No module changed.

and the screen remains as per the screenshot.

I'm using RN 0.41.2 and current master of react-native-openpgp and it has been react-native link'd accordingly. Oddly, there's no errors/exceptions or messages triggered in the debugger or console (even with using react-native start --verbose) aside from the output above. Let me know how one debugs something like this.

Thanks for sharing this code by the way; it's looking really helpful.

[eclesias]

I'm having the same issue with RN 0.40.0

[simonjk]

I have the same issue...
r-n 0.40.0
r-n-openpgp 1.0.3

[akyGit]

The same issue
RN 0.40.0
RN-openpgp 1.0.3

[simonjk]

@orhan Any news on this? this is a royal pain in the A.... and makes the library almost unusable

[theinventor]

👍 bump

[srinivasdamam]

same issue here, has anyone found the workaround.

[srinivasdamam]

@theinventor which version did it work for you? I have 0.42.0 still it doesn't work