Recently we noticed an issue with the Notifications of our Expo app on Android.
The app takes about 6-7 seconds to display when opened by tapping the notification while the app is in background. Here I mean display, the app goes into active mode immediately. Thus, a pop-up modal that should appear on screen for 2-3 is missed completely by the user.
The last good version was built on Oct 18th. Hardly any changes are made after that. We even tried undoing each change to see what might have impacted, the issue remained.
Other thing noticed is Oct 18th version apk file is 27 MB while any newer version is 18-19 MB.
Anything that might have changed with Expo Build during this period (post October 18)? Also, anyone had any freak experience with Expo build apks recently?
PS: Only warning seen recently in Dev Mode is
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 change listeners added. Use emitter.setMaxListeners() to increase limit but we haven’t added any listeners recently and there is only 1, the Notifications listener, that too had been added months ago.
Hi have got the same issue today I have published my app 7 days ago. after resolving some problem with my maps I have tried to re-publish the project and I have met the same issue. As I am using MobX in the my project I want to see if the problem is not not coming from there because I have added 2 new @observable elements in my store
Tried, with updated Expo SDK 30.0.0. Issue remains. The new app is 19 MB while older builds were around 25 MBs.
What was changed recently in building the app?
Hello, any updates here? I have got the same issue in the development mode with expo SDK 32.0.0. And my ios and android builds became much smaller…
This is a result of builds only containing the SDK version the project is running. You can read more about this in the blog post here: https://blog.expo.io/expo-sdk-v31-0-0-is-now-available-cad6d0463f49
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 change listeners added. Use emitter.setMaxListeners() to increase limit warning?
Please open a new forum post when bringing up a new topic so other developers can find it by searching!
Thanks. The size reduction itself is not an issue, in fact a good thing. But we suspect it might have impacted on the build output. Discussion related to this issue also here https://github.com/expo/expo/issues/3182#issuecomment-456346363
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.