#hooky
1 messages ยท Page 1 of 1 (latest)
Hi ๐
Just so I'm clear. You submit a new release for review, it gets rejected, you make the adjustments to the app and re-submit
And you are trying to re-submit without changing the app version?
What I wanted to double-check was: what does "re-submit" mean? After fixing the issues, I just do the steps all over again, right?: Create a new version, and submit. Right?
I was curious if I was supposed to do that, to expedite the review process or something.
So concretely: I submitted version 0.0.23. Got rejected.
Now I fixed the issue.
So now I submit version 0.0.24 with the fixes. Right?
(Now that I think of it, I suppose every time I run stripe apps upload a new version is created... so my question is kind of silly. Right? ๐ )
Yeah that doesn't seem like a good dev experience.
Oh I wasn't complaining. ๐ I was just wondering if I was doing it right.
I wondered if there was some "resubmit 0.0.23 with your fixes" option that I missed. There isn't, right?
Yeah I just tested on my own test app and it does require you to bump the version number for every stripe apps upload. I think this might be required but let me double check
Okay confirmed, if you changed anything in the code you will need to use stripe apps upload and bump the version number
Excellent! As I suspected! ๐ Thanks a lot.