I am trying to enable GoogleSignin in my React Native app for Android, which does not use Firebase. However, when I go through the "Configure a Project" process in the Google SignIn for Android console (found here: https://developers.google.com/identity/sign-in/android/start-integrating) to generate a google-services.json file, I instead get a credentials.json file.
The schemas are different and I already tried renaming the credentials.json to google-services.json but to no avail. Furthermore, when I click the "Configure a Project" button again, I now get a pop up saying "Something went wrong. Please try again later." In my browser console I see that it is a 409 error.
How can I generate the google-services.json file for a non Firebase project?
I don't think it's possible to do this without Firebase. I was under the impression that if I wasn't using a Firebase database that it wouldn't be a good idea to register my app there. But, it seems like Firebase and Google have partnered over this so I went ahead and did it anyway and got the google-services.json that I needed (and still not using Firebase for my db).
Related
I'm currently getting the error in the subject line. I'm currently using RN 0.61.2. I'm using a bare React Native project but I had to install some expo dependencies in order to implement the "Sign In with Apple" button via expo-apple-authentication and I think that's what might be causing the issue.
The "Sign In with Apple" button works as expected in my ios emulator but I get an email with this error when I upload the app to App Store Connect. The following github issue thread is a close match to my issue:
https://github.com/facebook/react-native/issues/26255
The following post recommends adding a post_install hook to remove UIWebView and has a lot of upvotes but the path mentioned in the post doesn't exist on my system so this post_install hook doesn't work for me:
https://github.com/facebook/react-native/issues/26255#issuecomment-528275747
The following post in the github issue thread also has a lot of upvotes:
https://github.com/facebook/react-native/issues/26255#issuecomment-527447318
However, App Store Connect still returns the same error for the uploaded app after I execute this command. Any recommendations on what I can try at this point in order to get my app successfully uploaded to App Store Connect?
I have created a react-native app using expo. Now I am looking for share-extension to the app to import CSV data from email attachment to my app.
I have tried npm package but that does not work for me(I was not able to build my project with that npm package in Xcode)
I think react-native or expo does not have any share API
In this picture, you can see how he got the option to import data into the app.
I understand that without share extension API, I think react-native and Expo both are useless because you can create the app but you don't expand it.
Looking for the solution or any other alternate solution.
I'm afraid this is not possible with expo.
First of all, are you looking for a way to create your own extension, or do you just want your app to be in the "open with list" that you have in the screenshot on the right? (Sharing and "open with" are two distinct things.)
If you just want your app to be listed in the standard "open with list", you do not need to use github.com/alinz/react-native-share-extension since it serves a different purpose. To quote the repo:
This is a helper module which brings react native as an engine to drive share extension for your app.
So with the package you can use react native to create your own share extension
To get your app into the "open with list", you need to go to target settings and change it according to the screenshot (example for MS word). Read more about it here. However, I'm afraid you won't be able to do this with expo without ejecting.
How to get the url of the file in react-native? You need to make sure that libRCTLinking.a is in the Link Binary with Libraries in Xcode (it'll probably be there already). And then you can follow the docs and call Linking.getInitialURL to get the file url. Then it really depends on what you want to do with the file. If you need something complicated, you'll likely need to write native code. If you just want to upload the file to some server, then you can make use of blob support that was added to RN 0.54 in this commit. An example of how to use the blob support is here.
I am submitting react native(expo) project to app store. I got to the step where I am told that my app uses IDFA and I had to tick some boxes so that I can confirm that I am using them which in fact is not true.
From research I found out that expo uses analytics tools like Segment and Amplitude which is built in.
I would really prefer to say that I am not using the IDFA and I do not plan to use it in at all. How can I disable IDFA usage in my binary?
I was running into the same problem and I found this issue on the expo repository. It seems that right now it isn't possible to do that, so the easiest thing to do is check those boxes when submitting the app.
For some reason we needed to change the package-id of our existing android application. We already use Fabric for Crashlytics.
I'm trying to bring that new app up in the Fabric dashboard, but it's not showing there, despite the device log showing no issues (as fas as I can see): device log
Any ideas why the new package-id isn't visible in our dashboard?
Best,
Sven
I experienced a very similar issue to this when building an app with multiple flavours. The solution is to manually specify the package name, and not let Fabric try to automatically grab it, as it tries very hard to "stick" your old package name.
There is a full post available (disclaimer: my site), but essentially you need to use:
Fabric.with(
Fabric.Builder(this)
.kits(Crashlytics())
.appIdentifier(BuildConfig.APPLICATION_ID)
.build()
)
Make sure to include all dependencies on their dedicated gradle.build and meta in manifest file. Next is to throw a force runtime error on your device with internet connection also do not forget to initialize it first with Fabric.with(this,new Crashlytics()). If this doesn't work try to download and install Fabric for Android plugin in Android Studio, restart the IDE and you will see a fabric icon above. Start it and select your package name.
I had the exact same problem, in the log I clearly see that the Crashlytics is in use.
I/CrashlyticsCore: Crashlytics report upload complete: <ID>
But I cannot see my project on the dashboard, and always redirect to the tutorial.
After a Build-Clean and an Android studio restart, build and run the app again to my phone, and voilá, it finds itself. Now working, without any change.
I have the same problem. After hours of researches I resolve this for my application.
First: After adding new flavour, I make changes in Firebase console (added new app in existing project, with production SHA1, changed google-services.json).
After that app does not show in fabric dashboard and fabric plugin in Android Studio. Problem was resolved after linking new app in crashlitycs in firebase console. And after that check your roles, must have Owner role (on Firebase Console Project).
I am using Titanium Studio to build my application, i have got it released in app store for iPhone.
But now i am trying to publish this to Google Play store. Below are the steps i am following, please let me know if i am doing wrong
1) Created a Google Publisher account (to get access to Google Play console)
2) Build my application in Titanium Studio, and copied the app.apk file from /build/android/bin directory
3) Uploaded this app.apk file in Google play store
I know i should add more details like appicon, screenshots to the app before publishing it.
But is this the correct procedure? because i can see in some articles suggesting
to create private key to package app.apk file.
Please suggest.
balanv here is the link i have for signing APK for unity: http://answers.unity3d.com/questions/149094/android-apk-signing.html
OR one closer to your problem:
https://wiki.appcelerator.org/display/guides/Packaging+for+the+Android+Market
also look at https://wiki.appcelerator.org/display/guides/Packaging+for+the+Android+Market