-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-11-05] [$250] Upload logs from Swift code #42659
Comments
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989 |
Triggered auto assignment to @puneetlath ( |
Job added to Upwork: https://www.upwork.com/jobs/~018463b08116cdfa88 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
@puneetlath, @arosiclair, @abdulrahuman5196 Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
seems to be an internal assigned issue. Seems we don't have a PR yet. |
I wasn't able to find the root issue for this when I looked into it though I'm pretty sure it was a transient issue in the NotificationService for iOS. We do |
No progress on this yet |
Focusing on a critical issue atm. |
@puneetlath @arosiclair @abdulrahuman5196 this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.43-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-10-10. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
The PR has been reverted, being suspected to increase heating / CPU consumption: https://margelo.slack.com/archives/C01GTK53T8Q/p1727896624465699 |
Any ideas on what might be the issue? We didn't change much in our App code for this. Is there anything suspicious like a possible infinite loop in the |
Kiryl is OOO and back Monday next week to have a detailed look! |
@arosiclair probably Anyway I have some potential optimizations in my head that we can apply and significantly reduce overheating 👀 |
@arosiclair I fixed overheating issue - would you mind to review and test new PR revision? #51086 |
I'll take a look. What was the root problem? |
The operation with I re-worked code and made interval customizable. Since we want to intercept only push-notifications logs I disabled constant pulling from main app at all. I think such approach will significantly free up resources. However I don't know whether device will be overheated if you receive messages (i. e. notifications) frequently - that's something that would be good to test 🙌 |
Cool, nice work 👍. I'll review soon-ish. I have some higher priority projects to address atm though. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.54-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-11-05. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
No regression tests needed since this is just for logging. Thanks for the help @kirillzyusko! Closing this out. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.75-1
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @arosiclair
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1716825560361569
Action Performed:
User B logged in iOS device and notifications enabled
Expected Result:
The notification received with the user's avatar
Actual Result:
No avatar displays in the notification
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
1911951290129650
5005778300960326136
Relevant logs:
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @kirillzyuskoThe text was updated successfully, but these errors were encountered: