navigation-stack | Swift UI library | User Interface library

It is because of target SDK updated to 30, some features (eg: Speech recognition,TTS) works in from android 11 device only after adding following code in our AndroidManifest.xml

I'll try to cover most of the changes that are made.

Stack Navigation is done like below

Firebase Messaging on ios needs more configuration,

first, you need to add this import in AppDelegate.m: #import "RNFBMessagingModule.h"

then after this line: RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];

add this line: NSDictionary *appProperties = [RNFBMessagingModule addCustomPropsToUserProps:nil withLaunchOptions:launchOptions];

then you need to change the initialProperties in the RCTRootView from nil into appProperties so it will be like this:

RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge moduleName:@"RETUЯИ" initialProperties:appProperties]; <-- changed from nil into appProperties

After all, we need to add an APNs Authentication Key file in the firebase console.

go to project setting, then scroll down to see your ios app, you will see APNs Authentication Key title, you need to upload an authKey.p8 file or you can use the other two fields with the title APNs Certificates

the authKey.p8 file needs to be generated from app store connect

• Select Users and Access, and then select the API Keys tab.
• Click Generate API Key or the Add (+) button.
• Give a name to your key, tick the "Apple Push Notifications Service" box, and download
• Upload the .p8 file to the firebase console

of course, don't miss to add the GoogleService-info.plist file to your example.xcworkspace, you can see how to do that in rnfirebase.io

also, you need your Team id, and you can get it from the app store connect profile and you will see the key id after generateing it.

hope this will help you 🙏,

Regards

Your react-navigation-drawer version is conflicting with the version of react-native-reanimated. Try to run npm i --save react-native-reanimated@1.0.0.

Downgrade your react-native-reanimated to version 1.1.0 Run this command in terminal yarn add react-native-reanimated@1.0.0

Use it like this -

Working Example

Youtube Tutorial for Navigation Gestures

[Solved] Work for me Install below

I had this issue a few weeks ago, what a pain! In my case I had one dependency that was requiring background location without me noticing. Secondly, I had a wrong permission declaration on Google Play so my builds kept being rejected.

To do this I used the Merged Manifest inspector in Android Studio. This shows you what your manifest looks like after all project dependencies have been taken into account. Find ACCESS_BACKGROUND_LOCATION and double click on it, this will bring you to the actual manifest where it's requested. Scroll to the top of this file and the package=some.package.name should help you identify what it is. In my case the permission was requested by an old dependency I didn't use anymore so I just uninstalled it.

Note: if you're often working on different branches, make sure you have the correct dependencies installed and make a clean build before checking the merged manifest:

@Tobias shared this. https://github.com/expo/expo/issues/12603

SDK 41 contains all the necessary changes to make your app compatible with Android 11, and should not result in removal from the Play Store. There is no action for you to take. Just because you received this warning, does not mean your app is infringing on the new scoped storage policy. According to this response from someone at Google, they sent this warning to anyone using the requestLegacyExternalStorage flag since it is their best indicator of apps that may need to declare the MANAGE_EXTERNAL_STORAGE permission. No Expo libraries require the MANAGE_EXTERNAL_STORAGE permission.

If you're on SDK 41- you have nothing to do, you can ignore this warning. If you're on SDK 40 or below- you can ignore this warning since it's specific to targeting Android 11. Bare workflow- update to the most recent version of expo-image-picker, and make sure none of your other dependencies require the MANAGE_EXTERNAL_STORAGE permission (inspect your AndroidManifest.xml from a release APK).

You should double-check your Info.plist, You might have included something like this Privacy - Tracking Usage Description