Expo Go

Forcing users to update sdk from 51 to 52 that completely break code throughout the whole code base is not beneficial to anyone.

Expo makes my life so easy. I can work on my project at work. I open GitHub’s code space and spend my free time coding away.

I’m currently on a iPhone 12 and it loads the projects but when I try to press buttons it fails to respond to any kind of touch but on others phone it works perfectly so it isn’t my laptop !?

The app does not load any demo apps listed on expo site, it used to work before.

Excellent app. Love it

Fix the bugss ❗️

It used to work but now I get a “internet connection appears to be offline” error message even though I’m connected to the same wifi

Using Expo is one of the most incredible development experiences I have had in my 20 years of development. I feel sorry for mobile developers who don’t use it. Their job is so much harder and slower. It also solved the problem of my underpowered laptop and quickly took me from a react developer to a mobile app developer!

This app is so helpful!! It is awesome how you can see your edits as they occur! I also like how you can just send the app and information to people to have them test it and they have no problems!!

This app is really cool but last night it really made me super angry. It has a very serious bug, that should be addressed. whenever I open scan any code to open any react app. It does not let the user touch the elements on the screen, if there are scrollview or flatlist, you cannot scroll if there are buttons, switches or any direct interactive elements you cannot touch because there is a layer on the top which needs to be removed to touch the elements in the app. This is actually the developers menu which loads on startup but for some reason is not visible. I tried a lot to touch the elements which never worked unless accidentally when I shake the mobile phone or I trapped with three fingers … there was a slight glimpse of a few buttons and then that disappeared and after that scrollview started working, then I redo the same thing and I figured out that there was a button layer on the top. Which should be fixed.