Firebase registration error in iOS by react native - ios

I'm trying to figure an error out with Firebase, bit it didn't work well.
Is there anyone to help me?
What I'm doing is :
building iOS app by react-native library
attaching Firebase on this native app
and it worked well in the first place until I CHANGED bundle identifier of my iOS app.
What I did is :
changed bundle identifier on info.plist
renamed folder structure
renamed scheme
renamed project and workspace name
and it turns out that everything works fine except the execution app on simulator.. :(
After succeeding build, when I try to execute app on simulator, error message comes out like the following :
7.1.0 - [Firebase/Performance][I-PRF100005] FIRInstallations error: Error Domain=com.firebase.installations Code=0 "Underlying error: 작업을 완료할 수 없습니다. SecItemCopyMatching (-34018)" UserInfo={NSLocalizedFailureReason=Underlying error: 작업을 완료할 수 없습니다. SecItemCopyMatching (-34018), NSUnderlyingError=0x6000018be0a0 {Error Domain=com.gul.keychain.ErrorDomain Code=0 "SecItemCopyMatching (-34018)" UserInfo={NSLocalizedFailureReason=SecItemCopyMatching (-34018)}}}
7.1.0 - [Firebase/Performance][I-PRF710001] Unable to fetch configurations.
where the meaning of Korean word in the error message is "CANNOT FINISH THE JOB."
it says "firebase installations error occurs." because it cannot fetch configurations.
What should I do to get rid of this error? please help.. I'm struggling with this about a week.
Thanks in advance.

You should not modify the GoogleServices-info.plist yourself.
If you changed the bundle ID for your app, define a new app in your Firebase project, download the updated plist and use that to replace the previous one.

I found an answer. After I changed Firebase config file, GoogleServices-info.plist, What should I do is CLEAN ALL THE PROJECT.
Even cleaning build in Xcode, deintegrating pod file, reset yarn node_modules folder, they're not enough.
What I did is :
npx react-native-clean-project and cleaned all the options.
then the error is gone.

Related

How to resolve Azure Devops with iOS : Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6

Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6Error: Error Domain=com.apple.dt.IDEContainerErrorDomain Code=6 "Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder"." UserInfo={NSLocalizedDescription=Cannot open "Docs.docc" as a "Swift Package Folder" because it is already open as a "Folder
I was using Azure devops with iOS project , everything went well until this morning. It look like swift-log and SwiftProtoBuf SPM which called inside Firebase SPM cause this error.
I have heard there was a way to resolve this by disable caching in CI system , but i had no idea how to.
Update firebase to 10.3.0
Nothing resolve the issue
On our project, we are using MacStudio, also we have removed DerivedData and SPM repositories, which helped us. Also we have added some target to our project and on MacStudio, we manually made an archiving, to generate missing certifications.
Remove DerivedData - ~/Library/Developer/Xcode/DerivedData
Remove SPM repositories - ~/Library/Caches/org.swift.swiftpm/repositories
Manually archive the project
Than retry it from Azure.

Xcode error when uploading to App Store: “Invalid Bundle structure”

I'm using Xcode to build a native script app for iOS. I've registered an app on iTunes Connect.
when I build the application on Xcode its works well.
All goes well in Xcode until I upload to the App Store. I get the following error:
Your error is related with devDependencies, Since error is showing invalid bundle structure this is because some of your devDependencies is added in the dependencies object inside package.json.
In your case "nativescript-dev-sass": "^1.0.0-rc.2" dependency was added in your package.json just move it from dependecy to devDependency.
Open the project in Finder and search if you have added any .framework file in Project directory besides pod folder. Delete the .framwork file and build,archive again.

Shell script invocation error in Xcode 9

I've the following problem: I'm using Xcode 9.1 to build my Swift apps. Since a few days I got the error
shell script invocation error
everytime I want to compile the project. It's the only error which is displayed.
I already read some threads here and followed the instructions. F.e. I uninstalled CocaoaPods and reinstalled the latest version, I cleaned up the project, the right scheme is selected etc. But I can't get it to work.
Or is it maybe a problem that I have no iCloud keychain configured? A message with the question to store the "access" key was displayed once but I don't know if this is a problem of Xcode.
Tried it with:-
pod deintegrate
pod install

Unable to Connect Firebase to XCode App Using Swift

I have followed the instructions listed here. However, I am unable to connect my app to Firebase. I am new to iOS programming and have installed CocoaPods to add the dependency. I am receiving the error "No Such Module Firebase."
I had this problem too. Try cleaning the app and then building it. If not, upload a picture of your podfile.
Also, after installing the pod, you need to close XCode and launch your project through terminal by going to the project directory and running
open <YOUR-PROJECT-NAME>.xcworkspace
in order to get access to the pods.
Hope this helps.

After adding Watch Kit Target: com.apple.actool.errors "No such file or directory" with Image Assets

I just made a branch in my iOS project and added a target for an WatchKit App in there. When I hit build and run now I get this strange error:
: error: Failed to read file attributes for "/Users/philip.brechler/Documents/motortalk/ForumApp/ForumApp/Images.xcassets /Users/philip.brechler/Documents/motortalk/ForumApp/MOTOR-TALK WatchKit App/Images.xcassets /Users/philip.brechler/Documents/motortalk/ForumApp/MOTOR-TALK WatchKit Extension/Images.xcassets"
Failure Reason: No such file or directory
The directories exist of course and I didn't change anything else then adding the target. I also tried this twice with the same result. Any ideas?
Upgrading to the new version of Cocoapods fixed this for me.

Resources