Skip to content
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

Adapt to status-go backend changes for ConvertToKeycardAccount #15846

Merged
merged 1 commit into from
May 9, 2023

Conversation

qfrank
Copy link
Contributor

@qfrank qfrank commented May 9, 2023

@qfrank qfrank self-assigned this May 9, 2023
@status-im-auto
Copy link
Member

status-im-auto commented May 9, 2023

Jenkins Builds

Commit #️⃣ Finished (UTC) Duration Platform Result
✔️ bfd78fd #1 2023-05-09 10:27:18 ~9 min tests 📄log
✔️ bfd78fd #1 2023-05-09 10:27:34 ~10 min android 🤖apk 📲
✔️ bfd78fd #1 2023-05-09 10:27:41 ~10 min android-e2e 🤖apk 📲
✔️ bfd78fd #1 2023-05-09 10:29:10 ~11 min ios 📱ipa 📲
✔️ bd4e2b9 #2 2023-05-09 11:31:24 ~7 min tests 📄log
✔️ bd4e2b9 #2 2023-05-09 11:31:59 ~8 min android-e2e 🤖apk 📲
✔️ bd4e2b9 #2 2023-05-09 11:33:33 ~10 min android 🤖apk 📲
✔️ bd4e2b9 #2 2023-05-09 11:34:04 ~10 min ios 📱ipa 📲

@qfrank qfrank force-pushed the chore/adapt-change-to-ConvertToKeycardAccount branch from bfd78fd to bd4e2b9 Compare May 9, 2023 11:23
@ilmotta
Copy link
Contributor

ilmotta commented May 9, 2023

Thanks @qfrank, just now I faced an issue due to the signature change after pointing status-mobile to the latest status-go revision. My lesson learned so far (maybe obvious to you guys): don't rebase status-go against develop all the time, many times (like now) I had to spin off a new branch to start from the revision supported by status-mobile.

@qfrank qfrank merged commit c275205 into develop May 9, 2023
@qfrank qfrank deleted the chore/adapt-change-to-ConvertToKeycardAccount branch May 9, 2023 12:51
@qfrank
Copy link
Contributor Author

qfrank commented May 9, 2023

Thanks @qfrank, just now I faced an issue due to the signature change after pointing status-mobile to the latest status-go revision. My lesson learned so far (maybe obvious to you guys): don't rebase status-go against develop all the time, many times (like now) I had to spin off a new branch to start from the revision supported by status-mobile.

I see, thank you for your note 🫶 @ilmotta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants