-
Notifications
You must be signed in to change notification settings - Fork 0
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
Issue with Expo 44 #2
Comments
Hi @cmosboss Expo SDK 45 was released today. I'll upgrade this app and give it a go and let you know how it goes. |
I messed up the upgrade to begin with, but fixed it and it works fine. My Android dev client is here if you want to give it a try: https://expo.dev/accounts/wodin/projects/zip-test/builds/9a91e09c-2513-489c-84c0-14a89a944745 The error you're getting makes it sound like you don't have the native code in your dev client. It's the same sort of error I would expect from Expo Go, since that doesn't include the native code from Is it possible you built the dev client before installing Basically what I did was as you describe (except I didn't "publish" anything. Just installed the dev client on my phone):
Then you should be able to edit the JS to use |
Here's a "preview" Simulator build that works fine for me too: https://expo.dev/accounts/wodin/projects/zip-test/builds/69443994-5d2e-4bfd-88a2-147276cfb15f |
I just got the same block and found this issue here. I'm using Expo Go... I had in mind it would work :D I'm new to this expo thing, am I expecting something I shouldn't? |
Hi @tacitomv
|
Not sure if you ever ran into this issue before. Trying to add this to a new Expo 44 project. Everything seems to be working except when I try and actually run the unzip function on my custom development client I get this error.
Error: [TypeError: null is not an object (evaluating 'RNZipArchive.unzip')]
When configuring this did you do anything other than expo install react-native-zip-archive, publish your new development client, and then try and use the code?
The text was updated successfully, but these errors were encountered: