I'm now testing my project with TestFlight, I can see some logs (including checkpoint, session_start, etc) in SDK Debugger, but my reports are empty in Build. I send email to support#testflightapp.com, asked the question on Twitter, and even checked the tweets listed, but still cannot find the solution..I think SO is the only site I can refer to help now..
Have anyone met this issue before & solved now?? And btw, where is the TFLog? I cannot find any debug log that I set.
Thanks in advance!
EDIT:
Here're two screenshots that will show my issue clearly.
You see, I sent feedback, checkpoints (and there're also some session_stard/end logs), but no detail report. :(
SDK Debugger: The TestFlight SDK Debugger lets you see your team's SDK data before it hits our queues. The console also shows orphaned SDK events which can help you confirm you have implemented the SDK correctly.
So I think I implemented the SDK correctly. I tried both SDK v1.0 & v.0.8.3, and I build a new project for testing this service, same result.
How I wish I can offer bounty now!! Please help..
Finally, I got a reply from Testflight team:
To be blunt we've been having some stability issues which seem like they're the root cause of your trouble. The team is working as fast as they can to bring you a faster, more stable TestFlight.
unfortunately..
And I found the TFLog (tested reports from my simulator, but cannot receive reports for my device yet):
choose your desired build in Builds section;
choose Sessions in Reports section;
choose a desired tester, and you'll find some logs like:
click the blue INFO icon to open a detail dialog:
and at the top right corner, you'll find a Events button, click to open a selection area, then just select the Log and you'll get the TFLogs.
Just a heads up for anyone experiencing issues with the Testflight SDK not logging events at all.
Double check if you are also using Flurry for Analytics and see if disabling it solves the problem (it did for me). I read somewhere that this is a known issue with the way exception handlers have been implemented on Testflight SDK.
Related
I have downloaded the Nearby Interactions project that Apple released here. When I try to run the application I get this error
I have not modified the original project and there is nothing in the ReadMe that details extra setup configuration. Only that certain devices can be used.
There are no logs to accompany this and so I'm not quite sure on the cause of this. I see others have been able to run the project and so wondering if anyone has any insight into this
Running on an iPhone 14 device
Also, as a side to this, if anyone has any example app they have built with Nearby Interactions but in SwiftUI I would love to see how you integrated it in.
Thanks!
I had completed a Flutter app, which seems to work well in simulator. I then went on to release the initial version of the app to AppStore Connect and sent it to beta testers via TestFlight and they were able to test it without any issue and sent me some feedback.
I made a few changes to the app based on the feedback (nothing too drastic) and tested it throughly in the simulator which seems to work fine. But now when the users download the app via TestFlight it crashed while opening and I cant seem to fix it no matter what I try. Any help would be really appreciated
So far I have tried,
Followed this article letter to letter
Modify optimisation parameters in Build Settings as mentioned here
Tried this SO answer
Crash report from XCode is not much of use since it is not very readable (as attached in the picture).
Can't yet seem to find any reliable answer, Any help on this would be much appreciated.
I'm developing an app and am ready to release it to a small group (5) of testers for internal testing, so I added their Gmail addresses to the list:
I sent one of the testers the link to the app and after opening email and selecting the link, they got this:
followed by this:
So far, so good. Now when I select the tester in question, instead of advancing to the next page, which is the start of a tutorial (as the app does when it's run from Android Studio), it returns to the previous screen. No error message or crash (I checked with Crashlytics). Anyone have any idea why this is happening?
UPDATE: I added Firebase event logging to my app and saw that no events are being logged from the LoginActivity (on the other hand, when I install the app via Android Studio, events DO get logged). Logcat shows a NameNotFoundException thrown by the PackageManager for for the app's package. Thinking the package manager doesn't like app bundles, I generated an APK instead, but got the same problem.
UPDATE #2: The next thing I tried was re-installing the app via Android Studio. When I simply let the app run, it exhibited the same problem, but if I ran it in Debug mode, it was fine. Not a solution, just a clue.
If I don't get this resolved by this weekend, I'll have to email my testers the APK. I wish someone in the Firebase group were monitoring this problem because emailing APKs as a workaround really sucks!
UPDATE #3: Getting closer to the cause of the problem. The reason that events weren't getting logged in LoginActivity was because I was using a reserved event name: user event names cannot start with "google". After fixing that, events did start getting logged, including an ApiException "10:" when trying to log into a Google account. So I googled around and I THINK the bottom line is that when I opted into Google App Signing I may have uploaded the wrong app signing key. If that's the case, how do I upload the correct one? I hope the answer isn't "create a new app with a different package name and start over".
After opting in to App Signing, I neglected to copy the SHA-1 fingerprint into my Firebase settings. Also, I needed to rebuild the app with the updated google-services.json. After doing all that and updating the release, the opt-in link worked fine.
I have been trying to make the new iOS extension Unwanted Communication Reporting work. Currently I couldn't find any good walk-through tutorial or code-sample to make it work. Above that by just firing up a new project with this extension and building it shows me the option of reporting in the Phone App but not on the Messages app, Moreover, the option to enable it only appears in phone app but it says "sms/phone" so I think this should work for both of them.
I know its in beta right now but just want to know if anyone had any luck with it. Also, There is no code to share as its just the boiler plate that comes with the new project.
This might have been a personal issue. I reset the whole phone and now I can see the options to report message. Apple might have fixed it in their latest iOS build or it might have just been my device issue.
Apple's developer site specifies ”SMS and call spam reporting," which is an app extension that you will have the option of turning on or off.
You may enable an Unwanted Communication extension in the Settings app. I am not sure if Apple will utilize this but i know for android - screen turns red when such spam calls come in, also caller id notes that but currently apple seems to have found a middle ground.
The following worked for me, you can try:
Remove command definition for this in Plist file.
Delete the Target in project (you can delete code folder).
I am an iOS developer, and recently I try to find a tool to track crashes in our project.
After I integrated Crashlytics in my demo, I forced the demo to
crash for some times and check if the data in Crashlytics is correct.
But then I am confused by the data on the dashboard because the
percentage of 'CRASH-FREE SESSIONS' is always '<1%', while the total
number of crashes is 65.
Even I launch my demo and then kill it without crash it for several
time, the '<1%' doesn't change.
Is it a bug of Crashlytics?
I have sent 3 email to support#fabric.io, but did not get any reply. I don't know what is going on here.
That depends on your users. I had the same problem because I was testing it within my simulator and my iOS device, fabric is a service made by google. It's impossible to find a bug like that-- rest assured. Submit your app. Let your users use it, the actual result will come in a week
Hope this helps