The issue can be easily summarized with the following screenshot: The issue we're talking about is related to the installation phase of the Win10SDK module, precisely Win10SDK_3 at the time of writing - but we know that the issue also happened before and will most likely happen with future versions of the Win10SDK package as well. As you can easily notice, the installation phase is splitted into 2 steps: the download, which happen first, and the actual install. Yes, as many logs as possible, please: as specified above, ideally we need the trace level for Realm logs, if it’s difficult to collect in the standard console, you can use a custom class, as I did in our sample code.If you've stumbled upon this post, it most likely means that you're trying to install or update Visual Studio 2017 Community or Enterprise using the Visual Studio Installer tool.Same for Android SDK, Realm SDK, Expo, React Native, ….The Linux distribution/version you’re using.I’ve almost enough to put together an internal ticket to investigate: could you please specify At this time, we don’t know if it’s just Linux, either, but I’d assume it may be, as we’d likely have many more occurrences reported otherwise. This seems to reinforce the hypothesis that’s not a Realm SDK issue in itself, but more an environment conflict, almost certainly limited to Android (it’s a Google library) and to the expo-dev-client (it works with eas). That’s indeed useful information: it’s interesting to notice that nowhere in the stack trace there’s a sign of the Realm SDK, it’s a TikTok (?) library that crashes instead. : Can't get WAA status for Mavatar! : : Attempt to invoke virtual method ' ()' on a null object reference : at .dataservice.z.b(PG:1) : at .dataservice.at.a(PG:1) : at .tracing.ed.a(PG:2) : at .concurrent.aj.a(PG:2) : at .concurrent.ac.apply(PG:1) : at .concurrent.h.e(PG:2) : at .concurrent.j.run(PG:9) : at .concurrent.bf.execute(PG:1) : at .concurrent.d.i(PG:1) : at .concurrent.d.l(PG:12) : at .concurrent.d.n(PG:2) : at .concurrent.i.f(PG:1) : at .concurrent.j.run(PG:13) : at .i.af.run(PG:1) : at .i.an.run(PG:23) : at .i.l.run(PG:2) : at .i.q.run(PG:4) : at (Thread.java:923)
Logcat gives a ton of information but I’m able to get the following error (I can provide a more detailed log if this isn’t helpful): Hi I would like to add my experience to this conversion as I’m in the same boat.Ĭreated a new project using the Expo template code only, ran the command: expo run:android with the Android Studio Emulator open, the development build opens no problem but as soon as I try to add a new entry, the app crashes without error.
0 kommentar(er)
