DEV Community

Expo SDK 40 is now available

Expo Team on December 09, 2020

Today we’re announcing our fourth and final SDK release of 2020, Expo SDK 40. SDK 40 includes React Native 0.63, mostly the same version as SDK 39 ...
Read full post
Collapse
 
wobsoriano profile image
Robert • • Edited

This is awesome! Something good happened at least this year lol.

BTW I have an expo 39 project, installed the latest expo-cli 4.0.12, ran expo upgrade, and still get 39 (cli saying I have already installed the latest version). Any idea?

To confirm, I have 4.0.12 successfully installed after running expo --version.

UPDATE: After an hour, running expo upgrade shows me sdk 40! thanks

Collapse
 
brentvatne profile image
Brent Vatne •

sorry about that! we pushed an update to expo-cli to force invalidating our versions cache when running expo upgrade so this won't happen in the future

Collapse
 
5ervant profile image
Mark Anthony B. Dungo • • Edited

Looks like, it's not easy to upgrade..
From "expo": "~36.0.0" to "expo": "^40.0.0".

Exception
TypeError: undefined is not an object (evaluating '_window$location.protocol')

C:\Users\USER...\PROJECT\node_modules\next\dist\next-server\lib\utils.js (3:193)

I'm using Next.js with Expo for Web.

Raised issue: github.com/expo/expo-cli/issues/3156

Collapse
 
arichayo profile image
arichayo • • Edited

I upgraded to expo 40 with the bare workflow and i published it as an update on the app store and google and now when i run expo-publish i don't see the changes being reflected like they were before.

Any clue as to why the OTA updates are not working?

Collapse
 
hanselsen profile image
Hans van den Elsen •

Do I understand it correctly that we should now be able to run expo eject for bare workflows? That would be so awesome!
When I run it after the successful upgrade (had only to remove yarn.lock), I get an error:

\ Config syncingAndroidManifest.xml mod error:
Invalid character in entity name
Line: 26
Column: 172
Char: =
Enter fullscreen mode Exit fullscreen mode

Is there anything I'm missing?

Collapse
 
expoteam profile image
Expo Team •

hi there! you can run expo eject in bare projects but ymmv - we aren't optimizing for this case right now. run it with EXPO_DEBUG=1 expo eject to see more info about the error.

Collapse
 
tsusubk profile image
tsusubk •

Hi. May I ask, regarding the Deploying to App Stores guide, is IDFA thing and/or newly one started on Dec 8 related to only Managed workflow or both the workflows? 🤔 Thanks!! 🙏

Collapse
 
animeeples profile image
jonliak •

Hello! The policy to disclose the use of IDFA and data collected is required for all apps submitted to the Apple App Store. However, the guidance provided here is specifically for the Managed workflow. That said, some of the information might still be helpful for answering the privacy questions even if you are using the Bare workflow.

Collapse
 
sebastianwirkert profile image
Sebastian Wirkert • • Edited

Thanks for the good work. Is this likely to change in future releases?

If I understand this correctly, answering yes to IDFA will result in an ugly popup after installing. I would like to avoid this, especially if I don't use any of the functionality.

Collapse
 
tsusubk profile image
tsusubk •

Thanks sir for your help. It's my first app, and don't finish yet. :D

Collapse
 
aiahsan profile image
aiahsan •

lottie animation is still in danger zone any news regarding to it and we really need WebRTC for expo

Collapse
 
khj222 profile image
khj222 • • Edited

I'm envious of apps that have successfully upgraded. I got a problem doing it apparently, it is caused by expo-notification and no solution or information on the forum or Google.

Collapse
 
sturdynut profile image
Matti Salokangas •

Just upgraded from SDK 39 to 40 without any issues. Thank you for the great release notes and all the hard work!! 👏 🎉 🍻