New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is AndroidX migration complete? #756
Comments
have the same error |
Hi same error for me |
Same error here. Any solution? |
It seems to be version 61 of react native. Version 61 has different interface for WritableMap, which expects String,ReadableMap instead of String,WritableMap. |
WritableMap extends Readable map, so, IIRC, that should still be fine. FWIW, that change happened in v0.61.0, so in theory it should work fine with v0.60.6; however, I haven't tested it yet as I abandoned the v0.60+ upgrade for a while longer until a couple of my dependencies catch up. |
I can confirm that in my case on RN v0.60.5 it is still working, while on 0.61.1 and 0.61.2 I encounter the crash mentioned above (with putMap parameters mismatch, introduced with: facebook/react-native@1a29371#diff-5c34d514dda20c19b42e599a840ba0a5 ). I have tried to work a temporary workaround: created a fork from master, rebuilt it against react-native sources of v0.61.2, took viro_renderer aar from current official release (v2.17.0) and managed to get a working package. At least it seems to be working for my used feature subset. Here's the package, if you want to use it as a temporary workaround before this issue gets fixed properly: |
@Iskander508 Did you also grab the latest iOS framework? Otherwise you'll still need an API key for iOS. I haven't tested it with your package, as I built my own 0.61.2 version in a private NPM repo as I needed to fix some other problems too. I did forget to include the iOS framework initially. In case people want to use your workaround, that could be helpful for them. |
Yes, this package probably still needs an API key provided. I noticed that too. |
@Iskander508 Did you manage to get Viro Media working on Android and RN0.60.5? We've updated our project some time ago to 0.60.5 and everything's working ok on iOS but Android is a pain in the a$$. Haven't had any luck in getting it working yet. If you have any advice how you actually did that would be awesome. |
I'm running RN 0.61.2 now, but the integration is probably the same: As far as I can see here are my changes:
|
@Iskander508 Thanks for sharing your setup! I've been following the steps for integrating with existing projects and got myself in a situation where the app builds fine but when opening a ViroScene it gives me an error |
It works! I made exactly the above stpes that @Iskander508 suggested and with a quick Viro360Image test it is working. Oh this is so cool! Been trying to get this working for some time now with RN 0.60.+ |
@Iskander508 this seems to still be crashing on RN 0.61, can you confirm? |
Same issue "react-native": "0.61.5", |
…o as per viromedia/viro#756 (comment) and changing how that is setup so that it can working with the stack navigation (it seem to require the ARScene Navigator)
Hi @Iskander508 , in my case is working correctly in Android and RN 0.60.5. (if needed i'll try in 0.61.2 like you) |
Yes, we got it working also on iOS. We followed these instructions. Our changes are:
|
@Iskander508 Thank you! |
will it work for react native latest version (0.63.3) |
I tried it on latest react native version (0.63.3) its crashing and throwing an exception:
|
It seems each time rn is upgraded, even if it's minor, you'll need to rebuild react-viro by running the |
Did you clone the project https://github.com/viromedia/viro.git and executed the |
Environment
Please provide the following information about your environment:
Mac
Android 9.0
viro: 2.16.0
RN: 0.61.2
Samsung Galaxy S8
Description
When attempting to open the AR screen after upgrading to RN61 the app crashes with this stacktrace:
On a hunch, I disabled jetifier for react-viro thinking it might be causing a weird rewrite, but when attempting to open the AR screen now the app still crashes, but with a class not found exception for an old support library.
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, screen capture, video recording. The more information you provide, the better we can support you.
The text was updated successfully, but these errors were encountered: