Filtering version numbers bigger than 99
holgersindbaek
Posted on
Jun 13 2016
I'm trying to filter for the testflight version of my app, but it doesn't seem like that is possible with Raygun for version numbers bigger than 99:
Can someone confirm that this is true? How do I get around this?
Alex
Posted on
Jun 13 2016
Hi Holgerindbaek,
You should be able to filter by any version given that at least one error with that version has been received by Raygun. If the version you are trying to filter by doesn't appear in the filter list it probably means we haven't received any error reports from that specific version of your application yet.
Hope that explains things.
Best regards,
Alex
holgersindbaek
Posted on
Jun 13 2016
Hmm ok. I just implemented Firebase new crash reporting tool. Could that potentially stop the Raygun SDK from sending crash reports?
holgersindbaek
Posted on
Jun 13 2016
Can confirm that the version number is not appearing in the filter list. This is a bug that was just sent to Raygun (from the simulator) and looking through the filter list, it can't find any bugs with the 2.9.102 version number.
Alex
Posted on
Jun 13 2016
Hmm, thanks for the link, it definitely looks like there is an issue.
We'll have a look and get back to you once we've got a solution.
Alex
Posted on
Jun 13 2016
Hi,
Just thought I'd update you to the situation. It appears that some errors over the past three days weren't indexed properly for searching or filtering. This issue has been resolved and all errors which weren't indexed correctly are going to be reprocessed. The reprocessing may take some time so I'll post again once this process has completed.
Thanks for your patience and sorry for any inconvenience.
Regards,
Alex
John-Daniel Trask
Raygun
Posted on
Jun 14 2016
Just a quick note: in iOS, only one crash reporter can be attached at a time. It's a platform limitation, not a Raygun limitation. There is a good chance that if you have attached the Firebase Crash Reporting that it would impact Raygun's ability to crash report.
Kind regards,
John-Daniel
Alex
Posted on
Jun 17 2016
Sorry for the late response. Just letting you know indexing has been regenerated for the affected error reports.
Apologies for any inconvenience this caused.
Best regards,
Alex