-
-
Notifications
You must be signed in to change notification settings - Fork 32
IllegalArgumentException: timestamp is not ISO format #407
Comments
Here's the complete adb log: https://pastebin.com/XnYi2EEb |
hey @lefoy thanks for raising this. Do you have a we can see in the logs The log: |
hey thanks for the update, I don't have a
|
@lefoy |
@lefoy btw are you able to intercept this call: and send me the content of this |
I am not calling |
I'm having trouble logging the entire string. I have to admit I'm not very familiar with Java. Here's my code and log:
|
@lefoy the String is being truncated. What's about doing:
instead of |
Ok I think I got it, here's the string, I hope I got everything:
|
@marandaneto thank for you help so far, I really appreciate the quick replies, let me know if you need more information |
@lefoy no worries, the problem is the breadcrumbs list, still trying to figure this out. the eg it should be something like the look this one: I'd double-check your data structure for breadcrumbs and it should be fine. |
Alright thank you for your help again, I will check my breadcrumbs |
Yes I can confirm it's working great when I disabled my breadcrumb 👍 |
@lefoy cool. one of them is also an array but not a map glad to help, have a good one. |
Just to give a bit of background on how we ended up with breadcrumbs like that in case someone is in the same situation someday and finds this on Google. We were using a logging system like Bugfender before and we had a bunch of custom log in our app to help debug our clients. We were logging strings, objects, booleans etc. We found out about Sentry and immediately wanted to try it out because we loved the way the stacktrace and errors were displayed. Before we can drop our current logging system, we wanted to log both in Sentry and Bugfender for a while so we added a breadcrumb for each custom log we had, but as we found out, it doesn't work well with all the different type of logs we had. We will update our breadcrumbs to make sure they all follow the correct type and it should work as expected 👍 |
yeah, you just need to double-check the data structure and that's it, everything else was correct, good luck and have a good one. |
Platform:
0.61.5
IDE:
VS Code
Build system:
Android Gradle Plugin:
I'm not sure on this one
Sentry Android Gradle Plugin:
Again I'm not sure on this one, I'm using the react-native plugin but since the error is only on Android I'm reporting here
Proguard/R8:
sentry-android installed with:
It was installed with the react-native plugin
The version of sentry-android:
2.1.1
I have the following issue:
I'm trying to send errors to Sentry from my Android react-native app but the errors are not reported in Sentry. I'm using a Samsung S10 with android 10.
Steps to reproduce:
captureMessage
and
captureException
but native errors are not reported.Actual result:
Expected result:
===
If I can provide additional information please let me know and I will do so. I wasn't sure if I should report here or in the react-native repo, but since it's only on Android and I have a relevant adb log I thought I should post here. Thanks in advance for any help!
The text was updated successfully, but these errors were encountered: