Getting HostObject::get error
See original GitHub issueSummary
I followed instructions with automatic linking. It builds correctly.
Version | Latest |
Affected OS | Android |
OS Version | Pie |
Current behavior
I’m getting:
Exception in HostObject::get: < unknown > <unknown> deviceinfo.js:6:33
loadModuleImplementation require.js:331:6 …
when I use
console.log('-->', DeviceInfo.getUniqueID());
Expected behavior
I should get device id in console.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
Exception in Host Object::get: <propsName: RNFirebaseAuth ...
Issue. Hi Everyone, I got an error "Exception in Host Object::get: <propsName: RNFirebaseAuth> java.lang.NoClassDefFoundError: Failed resolution of: ...
Read more >Exception in HostObject - React Native Build Android
This error happens after my metro-bundler loads 100% ( and no error happens on the bundler console screen ). Thanks for everyone who...
Read more >FMC Network/Host Object using Rest API - error: SubType
Solved: Hello everyone, I need to create over 100 network/host objects in FMC. I'm trying to do through the Rest API.
Read more >[Solved]-Exception in HostObject::get(propName:RNfirebase)
You installed 'react-native-firebase' package so kindly note to remove(uninstall) it. According to the docs: First you need to install firebase package: npm ...
Read more >CoreWebView2.AddHostObjectToScript(String, Object) Method
Perform property get, or property set locally. You can use these methods to force getting or setting a property on the host object...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You will be very unhappy with that change in the long run. Examine the example/app/build.gradle file for the ext block and how version pinning/synchronization between modules is done as a best practice…
Hmm - @mcgloneleviROOT very sorry to hear about the lost time, but note that you did not use your ext variable in your resolutionStrategy 🤔
Also, I continue to believe the presence of a resolutionStrategy indicates some structural problem that should be fixed, and resolutionStrategy is just forcibly covering it up - but I also recognize that there are a limitless number of ways to build software and I am sure a few justify the use of resolutionStrategy like this. Which is to say - I would put a FIXME in that block if it were me, and I would review it everyone month or two to see if I could clean things up and still build
Good luck!