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

watches the wrong build #5

Open
nikmartin opened this issue Nov 17, 2017 · 13 comments
Open

watches the wrong build #5

nikmartin opened this issue Nov 17, 2017 · 13 comments
Assignees

Comments

@nikmartin
Copy link

nikmartin commented Nov 17, 2017

Each time I run watchbuild, I get a status in the terminal like:
Waiting 12 seconds for iTunes Connect to process the build 2.0.8 (2.0.8)... this might take a while...
which is the build I just uploaded. A minute or so later, I get the notification on my desktop:
Version 1.1.18 finished... which is an older build. The current build is still processing.

@joshdholtz
Copy link
Member

@nikmartin I am not able to replicate this at all 😕 Is this still an issue for you?

@nikmartin
Copy link
Author

It is, and here's the issue: the versioning in this project is out of order. There are earlier versions of an app of the same name in this clients account, with later version numbers, because the developer at the time didn't understand or use semver. So my current builds are a lower semver than older versions. Once i skipped ahead to later version numbers, the issue went away.

@joshdholtz
Copy link
Member

@nikmartin Ahhh, got it! I think I know the issue now 😊 I will look into 👌

@andrewgarn
Copy link

Seeing this issue as well. Is there a way to get watchbuild to look for a specific version?

Its picking a version uploaded years ago instead of the latest.

@joshdholtz joshdholtz self-assigned this Mar 25, 2021
@joshdholtz
Copy link
Member

@andrewgarn Yes yes, we can make that happen!

Quick question though... did you update to the latest version that was released earlier this week?

@andrewgarn
Copy link

Yes, 0.5 fixed the auth issue we were having previously. Thanks for that!

@rogerluan
Copy link
Member

Awesome! Thanks for confirming @andrewgarn 🤗

I'm closing this issue then. Let us know if you see any other issues after upgrading to v0.5.0 🙏

Cheers!

@andrewgarn
Copy link

To clarify, it fixed the auth issue in #17 but i'm still seeing it pick the wrong build after updating to 0.5.0

@rogerluan
Copy link
Member

Ah got it! Sorry about that!
Reopening

@rogerluan rogerluan reopened this Mar 28, 2021
@rogerluan
Copy link
Member

@andrewgarn are you facing this issue? #5 (comment)

@andrewgarn
Copy link

andrewgarn commented Jan 31, 2022

@andrewgarn are you facing this issue? #5 (comment)

Still an issue as of January 2022. There is an old build from years ago watchbuild picks instead of the one uploaded today. The version number (2.9) is also much earlier than the current version (9.3).

Checking App Store connect the very old (2.9) build seems to be stuck in Processing state. There is no way to cancel, expire or delete this build in the App Store Connect website.

Can we have watchbuild prioritise newer builds, or allow a version into watchbuild alongside bundle identifier?

Thanks

@ryzn0518
Copy link

@nikmartin
Since we upload appstore through the Private Key, how do we operate which user to use?

@nikmartin
Copy link
Author

@nikmartin
Since we upload appstore through the Private Key, how do we operate which user to use?

I have no idea. You may want to open a new issue, it doesn't seem related.

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

No branches or pull requests

5 participants