You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> Task :app:processDebugMainManifest FAILED
/home/expo/workingdir/build/android/app/src/debug/AndroidManifest.xml:28:18-86 Error:
Attribute application@appComponentFactory value=(androidx.core.app.CoreComponentFactory) from [androidx.core:core:1.12.0] AndroidManifest.xml:28:18-86
is also present at [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91 value=(android.support.v4.app.CoreComponentFactory).
Suggestion: add 'tools:replace="android:appComponentFactory"' to <application> element at AndroidManifest.xml:6:5-162 to override.
For context, earlier this week I had run in to this issue after Expo deployed an update to their bare native template that included the removal of enableJetifier, but it was later reverted because of the above build issue mentioned here: expo/expo#30725
The text was updated successfully, but these errors were encountered:
@leaguefun I ran into the same problem on RN 0.75.2 and removing the supportLibVersion really fixed the build. However, it seems to be something important, can we just get rid of it?
Hi,
Just letting the maintainers of this library know that the
enableJetifier
option will be removed from upstream React Native / Expo:facebook/react-native@14ccf6b
expo/expo@3774717#diff-c1abe9eea32a8e683dbea2f18a322cc0b8c5a4ce1a8da1719c6a9ddf29f79e3fL28
Because the
enableJetifier
option is removed, the following lines:react-native-iap/android/build.gradle
Lines 171 to 174 in 5615869
Resolves in a bare Expo SDK 51 app as the following:
Which results in the following error:
For context, earlier this week I had run in to this issue after Expo deployed an update to their bare native template that included the removal of
enableJetifier
, but it was later reverted because of the above build issue mentioned here: expo/expo#30725The text was updated successfully, but these errors were encountered: