Firebase Performance monitoring on iOS doesn't collect correct amount of samples

752 views
Skip to first unread message

Thomas W.

unread,
Jul 5, 2019, 5:06:26 AM7/5/19
to Firebase Google Group
Hi,

I just added the Firebase Performance monitoring to our app. After a couple of week I just see 14 Sample for our main endpoint, but according Google Analytics we have ~345k Sessions with multiple requests to the endpoint.

Can it be, that the performance monitoring is not working for our released version?
Or can this be a conflict with our custom URLProtocol implementation, so that your protocol is not able doing the monitoring?

In our PLIST file I disabled following features, since I only wanted to focus on the Performance measuring:
- FIREBASE_ANALYTICS_COLLECTION_ENABLED
- FirebaseScreenReportingEnabled
- GoogleUtilitiesAppDelegateProxyEnabled

I installed the SDK using CocoaPods

pod 'Firebase/Analytics', '~> 6.2'
pod 'Firebase/Performance', '~> 6.2'

The project was build using Xcode 10.2.1 with deployment target iOS 11.

Best,
Thomas

Viswanathan Munisamy

unread,
Jul 18, 2019, 10:50:55 AM7/18/19
to Firebase Google Group
Hi Thomas:

Thanks for reaching out. There could be different set of things happening here:

1. The endpoint you are trying to checkout, are they HTTP/HTTPS end points? If not - Performance Monitoring does not capture any non HTTP/HTTPS requests by default.
2. The network URLs are usually pattern mined (for privacy reasons) and they get listed in the network tab. Could it be a possibility that the end point is available across multiple patterns in the network tab?
3. The 14 samples you are looking in the console - is that in the last 24 hours or for a longer period of time? It might be helpful if you could share a screenshot.
4. Are these network requests made via NSURLConnection/NSURLSession. Ideally performance should work here. Just trying to make sure we are not missing anything in either of these.

Recently Firebase came out with version 6.4. Can you tryout with the recent version and see if this is already fixed?

Thanks,
Firebase Performance Team.
Reply all
Reply to author
Forward
0 new messages