Closed michaelloo closed 5 months ago
@michaelloo Thank you for reporting this issue! If I understand correctly, the only problem here is that you are receiving a warning message in the logs? And everything else is working as expected?
Hi @szokeasaurusrex , thank you for getting back to me.
There is another issue where the Xcode debugger is reporting slow frames:
[Sentry] [debug] [SentryFramesTracker:177] Capturing frozen frame starting at 1007812449099666.
[Sentry] [debug] [SentryFramesTracker:169] Capturing slow frame starting at 1007812467756791 (frame tracker: <SentryFramesTracker: 0x600002918460>).
But I am not seeing anything in the dashboard:
Good news! After testing a bit today, I've gotten an alert email:
But it seems to be missing the symbols file which makes sense given the warning I get in Xcode build phases as per original post.
P.S.: I am also curious as to why I did not receive alerts last week and only receiving them today?
Hi @michaelloo, I think I have figured out how to resolve your original problem.
Apparently, by default, Xcode runs Run Scripts inside a sandbox, which blocks access to all files within your project unless they are specified as inputs to the run script. So, solving your problem should be as simple as adding the .sentryclirc
as an input file to the run script, like so:
Please try adding the .sentryclirc
as an input file, and let me know whether doing so fixes your original problem! If it does, we will improve the error message and update the documentation, so that this solution is clear to all users.
There is another issue where the Xcode debugger is reporting slow frames
This output is generated by the Sentry-Cocoa SDK, not the Sentry CLI. I have forwarded your question to the team that maintains the Sentry-Cocoa SDK, and I will let you know as soon as I have a response from them. Alternatively, you may open an issue in the getsentry/sentry-cocoa repository.
But it seems to be missing the symbols file which makes sense given the warning I get in Xcode build phases as per original post.
Yes, the error message in the screenshot indicates that the debug file upload failed. Adding the .sentryclirc
as an input file to the run script should solve this problem.
P.S.: I am also curious as to why I did not receive alerts last week and only receiving them today?
There are many possible reasons why this could have happened. Perhaps your monthly Sentry quota had been exhausted last week, but was renewed this week, or you could have changed a configuration option somewhere. If you suspect a bug, you should open an issue in the getsentry/sentry repository.
On the slow frame issue: The log messages [Sentry] [debug] [SentryFramesTracker:177] Capturing frozen frame starting at ....
mean that the frames tracker stores slow frames information in its storage. Still, it only adds that info to currently running transactions or profiles. The SDK doesn't add the info anywhere if no profile or transaction is active. I changed the log message so it's not confusing https://github.com/getsentry/sentry-cocoa/pull/3570.
Hey @michaelloo, I saw you reacted with a 👍 to my last message. I assume that means you were able to fix the problem, so I will close the issue now, and I will open a new one so we remember to improve the error message and docs.
If you still need any further assistance here, please reopen the issue!
Environment
Steps to Reproduce
brew install getsentry/tools/sentry-wizard && sentry-wizard -i ios
and followed the prompt...App.swift
file on my Sentry project dashboard 👍Got the following warning in my logs:
.sentryclirc
file exists, has my auth token, has-rw-r--r--
permissions.Script in Xcode build phase is:
Expected Result
No warnings in the Xcode logs, or better warnings to tell me exactly what the problem is.
Actual Result
Got warnings in Xcode logs, whilst things seems to be working fine.
Logs