Google plist issue in Xcode 12 and Swift 5.3 - swift

I am using firebase for developing my app with Google Plist. While running I am getting below error, trying to add again and again but it's still getting error. Could anyone help me on this issue?
Error
Thread 1: "[FIRApp configure]; (FirebaseApp.configure() in Swift) could not find a valid GoogleService-Info.plist in your project.

As we discovered in the comment thread above, your plist file was named incorrectly. It needs to be named "GoogleService-Info.plist".
If you have downloaded this file or other Firebase plist files in the past, the names may have something appended to avoid collisions like "GoogleService-Info (1).plist", which needs to be renamed for the Firebase SDK to recognize it.

Related

Firebase is uploading & fetching data on another app server

I was working on 2 projects at a time. Everything was working fine but when I uploaded my data from my app to the firestore, it was not found in the firestore. After checking it I found that it is uploading my data to my another firebase app database. Please help me resolving the issue I cannot find the error. It was working fine before, now both the apps are crashing.
My best guess is that you switched up the files that contain the information on how to connect to Firebase between these projects.
If you recently created these apps, that data is likely in a firebase_options.dart file that was created by the flutterfire CLI command.
But otherwise the information may also be stored in a google-services.json file for Android, and a GoogleService-Info.plist file for iOS.
Whichever of these it is, you'll want to check the data in these files and update them to refer to the correct Firebase project for each app.

Firebase Connection Killed

I have integrated Firebase into my iOS project. I have been using Firebase for years across many projects. This specifically is using the Firestore. I can authenticate fine and write to the database. However, after the write is complete, even though it's successful, I receive the following message:
Firebase Database connection was forcefully killed by the server. Will not attempt reconnect. Reason: Firebase error. Please ensure that you spelled the name of your Firebase correctly
The bundleID was copied and pasted directly from the app to the Firebase setup. I even deleted the app from Firebase and created it again. I have downloaded the GoogleService-Info.plist and I checked that the bundle there matches the bundle of the app. I can see nothing wrong here and again functionality is working fine.
The only instance I saw of this message browsing around was with a non-US based developer and it was suggested that additional config was required. However, that is not the situation for me. What else might cause this error to be generated?
The error message seems to point towards Realtime Database, despite your interest in Cloud Firestore.
I recommend:
Making sure you're using the latest SDK. Old SDK versions (before mid 2020) might require the Realtime Database URL to be present in the plist file, which isn't always the case anymore.
If step 1 doesn't solve the problem, you can:
Force the creation of a Realtime Database instance in the Firebase console.
Download the updated plist file and add it to your project.
If you end up with the second solution, can you comment with the SDK version you're using, so that I can check for issues in that?

App Store Connect: ITMS-90492: Invalid WatchKit Support

I tried updating a stand alone WatchOS app to the App Store and got this message from iTunes after uploading it:
ITMS-90492: Invalid WatchKit Support - The file WK doesn’t have the correct code signature. Make sure you’re using the correct signature, rebuild your app using the current public (GM) version of Xcode, and resubmit it. Don’t just modify the code signature of WK.
I have uploaded previous version without a problem, so I think it might have something to do with using WKInterfaceDevice().play(.click) in my code which is new to the version uploaded, but I am not entirely sure, has anyone ran into a similar problem and how did you fix it?
This appears if you have XCode beta installed on your Mac. It doesn't have to run just its simple presence results in this artefact.

ArchiveInfo.plist has incorrect data

After building and archiving my application, I open up ArchiveInfo.plist that's in the folder with the app and it contains some invalid data. The Bundle Identifier is misspelled. I have looked around everywhere in my XCode project for the exact same misspelling, but cannot seem to find it. Any help?
I had first written the app in an old Xcode and for iOS 3 so when trying to submit it for iOS 4 it was having this problem. I just recreated the project.

Connecting CoreData to my App on an iPhone Device

I apologize ahead of time for what I'm sure is a complete newbie lapse. Running my iPhone app on iPhone simulator - no problem. But I loaded the app on an iPhone device for the first time and it appears as if the SQLite database I'm using (NSManagedObjectContext) isn't connected or didn't upload. The app installs but with no data. How do I get it all to upload and work on the device?
I appreciate any help.
lq
The first rule with Core Data is that you should never ever touch the store directly. It should be considered a black box and only accessed via the the Core Data APIs. Accessing the database directly is unsupported and can lead to data corruption.
What you should do instead is create a trivial desktop application (or command line is you are just importing from another source) and enter the data there. Once the data is entered then copy the sqlite file to your mobile application and include it in the bundle. That way you are accessing the file from Core Data. Since Apple can and does change the structure of that file without notice your application will be future proof.
update
If you have created a database using Core Data you can then take that sqlite file and add it to your Xcode project for your iPhone application. Xcode will then copy it into the app bundle when it compiles the project.
Looking a little deeper I found a link that answers my own question. So anyone with the same question, this solved the issue for me:
http://ablogontech.wordpress.com/2009/07/13/using-a-pre-populated-sqlite-database-with-core-data-on-iphone-os-3-0/