It’s amazing how you can come back to a problem with a fresh set of eyes, and of course months of additional experience under my belt, to knock it out of the park. I was not going to let it hold me back again. aab file without uploading to the Play Console to discover it to still not be working.įast forward about 6 months, seeing that Call To Action I had a conversation with my manager and decided it was time to figure out this bundling. I attempted to figure out the bundle but struggled at the time with how to test that. Of course, we were mid-release cycle without a lot of time to explore what was going on. We weren’t sure if this was to do with the bundle or Hermes at the moment. The users were able to successfully download the app from the PlayStore but it would never get beyond a white splash screen, just hanging out there with no feedback. At the time, the project I was working on was about a 50MB APK.Īfter enabling Hermes and creating my first bundle everything seemed to be working great locally! We uploaded successfully to the Play Console with much anticipation with our significantly reduced file size, sent to our users in our Alpha test group and experienced our first letdown: the app would NOT load. While we were at it, I decided we should work on figuring out those Android Bundles.
Facebook followed up with a blog post about this announcement and how you could take advantage I was sold and decided I was ready to dig in. So what were those missteps I experienced previously? After attending Chain React in July of 2019, I was stoked at the announcement of the Hermes engine to be released with React Native 0.61.
0 kommentar(er)
