Firebase Crashlytics - is it installed correctly? - xcode

I have moved over to Firebase in my XCode app and followed the instructions for the installation. There are no error messages and the Analytics seem to be working as I am getting some data showing in the Analytics Dashboard but I am not getting any information in the Crashlytics section even through I have forced a few crashes.
When I run the app in XCode I get the following line in the console:
[Firebase/Crashlytics] Version 4.1.0
So it would seem something is working. The only thing I am uncertain of is the exact entries in the Run Script section and I am imagine the error is there. This is probably a very basic question but I assume I have to replace some of the entries to suit my project/computer.
Any direction here would be helpful.

Related

Recently when I updated my application and App is rejected

Please Help Me Fix this issue.
Recently when I updated my application(OXOO movies streaming app) I receive this email from Play Console:
Your app contains content that doesn’t comply with the Device and Network Abuse policy. We found your app is using a non-compliant version of an SDK which contains code to download or install applications from unknown sources outside of Google Play.
The SDK can be identified using the classname com.dcastalia.localappupdate.DownloadApk.
Affected Version(s):
App Bundle:3, App Bundle:3, App Bundle:3
But I have checked everything but have not found anything like this in the application.
Please give me some advice to fix this.
It is really important for me to release an update.
remove
implementation 'com.github.Piashsarker:AndroidAppUpdateLibrary:1.0.3'
from your build.gradle

How to handle MISSING_PLUGIN_EXEPTION in Flutter with Firebase Core Plugin on IOS

for several days I have tried to link my Flutter app with Firebase Database. But unfortunately, whenever I want to start debugging the compiler gives back a missing plugin exemption concerning the firebase_core package. I have already seen some entries referring to this issue here on stack overflow but none of them worked for me.
I have already followed the instruction steps by the installation guide on Firebase and included the Google Service File in my Xcode project.
I already did flutter clean, deleted the pods folder and the pod file.lock file in IOS, tried to include the Firebase SDK package by using the add package option in Xcode.
In the past, the connection between my Flutter project and the Firebase Database already worked but somehow it won't work now.
I think that my issue deals with the new step in the installation process for Firebase Connection when I am asked to make use of the Firebase SDK in Xcode.
In the following I'll add some more pictures for illustration. If someone had the same/a similar issue, it would be a huge help for me.
error Message
podfile
main_dart
Xcode runner workspace including google Service
AppDelegate in Xcode
pubspec yaml

Non-public API usage Flutter.framework/Flutter: _kCTFontOpticalSizeAttribute error on upload of flutter app

I've spent the last two days trying to submit my app to the App Store. I get the message below:
ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/Flutter.framework/Flutter: _kCTFontOpticalSizeAttribute. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/
Here's what Ive done so far:
a) I've scoured my code for any reference to Font Sizes - I had some that were constants - I changed the constant name to:
k_fontSizeMyName
b) I tried to download the latest flutter sdk version
c) I rebuilt my entire keychain.
Im so desperate right now. im tired.
What do I do?
the internet has no mention of this bug.
I've got the same message several times from the App Store Team a few minutes ago.
I think the problem was the Flutter SDK version...!
I used to use the latest version(Flutter SDK version 1.12.3-pre.26) at first but changed the Flutter SDK version to 'v1.9.1+hotfix.3' and the problem is resolved!!!
I solved the problem with the following instruction below:
Switching Flutter SDK version to 'v1.9.1+hotfix.3' with the command:
flutter version v1.9.1+hotfix.3
Archive and upload again ...
Problem Solved!!!!!! 🤩
This may be a recently-introduced Skia regression.
The code was included in Flutter v1.12.3, so v1.12.2 on the dev channel should work.
Flutter's Bad Build wiki page will be updated when there is a fix for this issue.
Update: This has been resolved in Flutter v1.12.5.
Since there have been a lot of problems with flutter recently(when I tried the fix mentioned in another answer I different error) I though I should include this https://github.com/flutter/flutter/releases
Just type flutter version [version code]

How do I archive/validate a Swift App that uses a framework in Xcode

I have an App that uses Admod and Firebase from Google. Since I am using Swift they want me to use frameworks when loading them from CocoaPods. When I try to archive/validate the App I get the error:
No suitable application records were found. Verify your bundle identifier 'org.cocoapods.GoogleToolboxForMac'
What is the correct way to provision an app that uses someone else's frameworks so it can be uploaded to iTunes Connect? I tried to find something in Apple's documentation but I haven't found anything.
UPDate:
I previously had answered my own question, since I had thought I had found a solution. My reply was:
Problem Solved. Turns out I was using an App-ID that I am having Apple look into as being corrupt. I had already created a new App-ID to prove the one I want to use is not working and retried with that and it Validates. This required a lot of help from the Google Ads Mobile SDK team. Thanks.
So the correct answer is: Now Incorrect
You should not get this error unless you are using a Bundle-ID that is not already registered on iTunes Connect, but, you should never be able to create an archive that does not have a Bundle-ID that is not already registered on iTunes Connect. So this is caused by an abnormal situation.
This is no longer true
I used my new working project and got 4 whole builds out of it and into iTunes Connect. In the process I was trying to clean up the mess caused by trying to solve this problem, like loosing my git history. I tried to modify my old App to get it to work and without modifying my new working project, But my new project started failing with the above error. I even used my time machine and went back to the directory as it was when I made the last build, but no help. So, any answers?
Further Update:
I pulled all the code related to Google Firebase and Admob out of the code and removed the cocoaPods and Archived/Validated and now I get the error:
You must supply a CFBundleIdentifer for this request.
Which is the error message I was getting with my other App-ID that tracked that App-ID in iTunesConnect. This time it does not track the App-ID so it must be something in my project. Will report what I find.
UpDate:
I think Apple has been modifying their code for validation at the same time I was trying different things. At one point it told me I was using CFBundleSignature instead of CFBundlePackageType set to APP and I fixed this and got the code to validate. Understand I am copying complete projects and renaming everything to debug this problem, so this must have come from the original program. I ended up with a project that was renamed from my original but archived/validated but when I went to compile for Test I got errors that I debugged until I got lots of Mach-O link errors. I decided to complete the loop and go back to my original code and try using the new Bundle-ID which points to the new App-ID, the one that works, and add all the knowledge I have learned. But when I get it done I have an project that can test but does not validate. The only difference is this project has the old identifier which has the same name as the suffix of the App-ID that has a bug.
Am I missing something?
Final UpDate?
On a whim I renamed the Scheme file to be the same as my Suffix to the Bundle-ID and I got my original Project to Validate! I have worked on this for over a month and you might not believe the astonishment I feel in this.
Back to Unit Test!
I have come to the conclusion that the Identity of the App, the name at the far top of the right side Utilities window, has something to do with the way iTunes Connect validates the App. This is the name in the left hand column of the Organizer window. It is like it overrides the suffix of the Bundle-ID and since I can't use that Identifier because the associated App-ID is corrupt. Or the name of the Scheme.

ITunesConnect - unable to select build

I am using Xcode 8 and I am trying to submit a newer version of my app to iTunesConnect. However I could not select any build version even though I tried to change the build number. See screenshot
I also tried waiting for a couple of hours with no impact.
Surprisingly Apple started sending out emails which tells you why your build wasn't accepted. I didn't see this email until the next day.
Dear developer,
We have discovered one or more issues with your recent delivery for . To process your delivery, the following issues must be corrected:
This app attempts to access privacy-sensitive data without a usage description. The app's Info.plist must contain an NSContactsUsageDescription key with a string value explaining to the user how the app uses this data.
Once these issues have been corrected, you can then redeliver the corrected binary.
Regards,
The App Store team
Once I fixed the issues and re-submitted the binary, I didn't see my build instantly. However after 10min or so, I get an email from Apple
iTunes Connect: Version 5.2 has completed processing.
Now when I look at iTunes .. the plus symbol next to the 'Build' section appears.
Hope this post helps others who run into the same issue.

Resources