[packages] fix another gradle 8 warnings (#22609)# Why there are other gradle 8 build warnings: ``` > Task :expo:processReleaseManifest package="expo.core" found in source AndroidManifest.x
[packages] fix another gradle 8 warnings (#22609)# Why there are other gradle 8 build warnings: ``` > Task :expo:processReleaseManifest package="expo.core" found in source AndroidManifest.xml: /home/runner/work/expo/expo/packages/expo/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. ``` # How migrate `package` in **AndroidManifest.xml** to `namespace` in **build.gradle** # Test Plan ci passed
show more ...
[expo-modules] Move code from `unimodules` into `expo-modules-core` (#13703)# Why Migrated `unimodules-core`, `unimodules-react-native-adapter`, `unimodules-app-loader` into `expo-modules-core`
[expo-modules] Move code from `unimodules` into `expo-modules-core` (#13703)# Why Migrated `unimodules-core`, `unimodules-react-native-adapter`, `unimodules-app-loader` into `expo-modules-core` # How - Change package using AS refactor tools - Fix some places where AS wasn't able to do automatically - Fix compatibility with new auto-linking - Ensure that classes which are used during installation steps are still available in the old place # Test Plan - expo-go (tested using unversioned and 41) - bare-expo
[android] Use stable manifest ID where applicable (#12964)
@mczernek/notifications suspended after 5 minutes (#9287)
@mczernek/app loader migration (#8438)* Fix overloading of AppLoaders condition. * Add information about AppLoader to AndroidManifest's meta-data and consume it in AppLoaderProvider. * Handle
@mczernek/app loader migration (#8438)* Fix overloading of AppLoaders condition. * Add information about AppLoader to AndroidManifest's meta-data and consume it in AppLoaderProvider. * Handle reinstalling of an application in task manager, even when ejecting in the meantime. * Update CHANGELOG.md * Move changelog entry to Bug Fixes. Fix typo. * Add some comments. * Resatrt alarm after reinstallation not only for startOnBoot option. * Remove waiting for debugger. * Fix CHANGELOGs. * Apply suggestions from code review Co-authored-by: Tomasz Sapeta <[email protected]> Co-authored-by: Tomasz Sapeta <[email protected]>
[unimodules-app-loader] Fixes Class Name Cache (#8292)
[AV][Android] Fix AV progress update (#7193)Co-Authored-By: Bartłomiej Bukowski <[email protected]>
[android] Do not strip HeadlessAppLoader constructors required by AppLoaderProvider (#7398)# Why Locally built SDK37 standalone app was failing to start with the following exception: > ``` >
[android] Do not strip HeadlessAppLoader constructors required by AppLoaderProvider (#7398)# Why Locally built SDK37 standalone app was failing to start with the following exception: > ``` > Attempt to invoke interface method 'boolean l.d.a.c.b(java.lang.String)' on a null object reference > ``` # How Inspecting the APK showed that this exception originates in `TaskService#isStartedByHeadlessLoader`, where `isRunning()` is called on `getAppLoader()`. We wouldn't expect `getAppLoader()` to ever be `null`, since: - `RNHeadlessAppLoader` is registered in the `@unimodules/react-native-adapter`'s package - `ExpoHeadlessAppLoader` is registered in `ExpoApplication` but it was. A few lines before this exception, a short error message was printed: `Expo: Cannot initialize app loader. <init> [class android.content.Context]` This, after some debugging, has led me to figure out that in production mode (this problem didn't occur in debug mode) ProGuard removes supposedly unused constructors of `RNHeadlessAppLoader` and `ExpoHeadlessAppLoader`. Adding a `@DoNotStrip` annotation to the constructors fixed the issue. I have also added: - `if (getAppLoader() == null)` checks to `TaskService` not to crash the application if, for some reason, app loader isn't there, - `e.printStackTrace()` to where the `Cannot initialize app loader. <init> [class android.content.Context]` was logged to help debug issues next time. # Test Plan On a separate branch I have applied this change, rebuilt the appropriate `expokit` Maven libraries, built a standalone app and it started without problems.
[android][task-manager] Task manager for bare in Expo (#6828)Task manager for bare android and iOS applications.