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

Build does not update if you delete a release and then upload new one with same version number #1746

Closed
MonkeyDoDev opened this issue Feb 22, 2024 · 2 comments · Fixed by #2254
Assignees
Labels
bug Something isn't working

Comments

@MonkeyDoDev
Copy link

App ID: 130984c0-a89c-44a0-972b-f29f9725b216

Description

I have a shorebird release for android with version number 1.1.55+73 which is good for use. So far, so good.

However, i am having some platform specific difficulty with my IOS version of that release. Because i want my Android and IOS build numbers to be consistent, my working flow whilst fixing/investigating my IOS issues is to

  1. delete the IOS build from that release (which i want to keep because the android version works)
  2. create a fixed IOS build with the same version/release number

However, when i do this.. the edits to the IOS build in subsequent submissions are NOT reflected when i run previews.

For example, i added some print logs to help me debug, but when i run preview after i released those changes, i was still seeing the OLD print logs when i run preview.

So it's as if the old original build i thought i had deleted is actually retained and never overwritten

Steps To Reproduce

  1. Create a release on both Android and IOS
  2. From the shorebird console, delete the IOS version of that release
  3. Change some code and create a NEW IOS release with the same version number

Expected Behavior

I would expect the code changes to be reflected when i run preview

@eseidel
Copy link
Contributor

eseidel commented Mar 29, 2024

Apologies for not replying sooner. I think the real fix here is #1762? Let me know if I've misunderstood.

@eseidel
Copy link
Contributor

eseidel commented Apr 17, 2024

It also occurs to me that if someone has ever made a patch to that release and uploads with a different version of Flutter that would be away to run into #1894. I guess if we're deleting all patches attached to a release when deleting that won't happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants