Issues updating marketplace entries?

Corona Marketplace Corona Community Plugins
#1

A long shot I know, but Corona’s on-site support chat is usually really helpful and at the moment seems to have gone awol so I’m hoping somebody can pick this up here?

In a nutshell, after our plugin was approved and went live on April 23rd, I pushed an update to the bitbucket repo on April 24th and created a new version within the marketplace. The update was just some performance improvements but in the marketplace release I updated the description part too, to include a quick sample for developers. Nothing that would really need approval, but I couldn’t save without hitting the request approval button again.

After a week or so I figured I’d just edit the original entry to include the same description update, because I could save that entry without requesting approval and hadn’t yet heard back.

On May 2nd I’d still not had any response so asked in the support chat and was told that there’s a bug with the approval request system at the moment.

May 11th I asked again on the live chat and this time haven’t had any response. The status of that message still shows as “not seen yet” so I’m thinking there’s probably an issue with the chat system now too!

So in summary, it’s been nearly a month now since I created a new version within the marketplace. This version isn’t approved yet and the description amend to the original entry still isn’t showing in the marketplace either. I assume that the repo sync went ahead ok on the 24th but I’m reluctant to push any further updates live until this all appears to be working, as there’s currently no way to inform developers of these updates.

Is anybody else experiencing issues like this? Or can somebody here please nudge the appropriate team to take a look at this for me?

#2

Hi,

I usually go through this channel for assistance, not sure if that would help or not http://support.coronalabs.com/helpdesk/Tickets/New

I don’t know how your plugin operates but I usually just update it in the repo, and then edit information (not resubmit) and save. Seems to work last few times I did it.

You really should have no need to “resubmit” if you have been given access to a repo for your plugin. You may also need to flush your browser cache to see changes. I generally add a “version” variable to a plugin so I can see when it has propagated from the repo.

-dev

#3

Thanks, I’ll give that ticket system a go!

I’m assuming that the update pushed to the repo will have synchronised just fine, but it’s the marketplace listing itself that I want to keep updated. https://marketplace.coronalabs.com/me/vendor/product has an “add new version” option alongside the edit option which I’d hoped would mean that when we add new features to the plugin, we can log them this way to keep developers informed. Admittedly we could just post updates to the website but it just seems silly to not make use of marketplace features really.

#4

Hi,

Yeah, I’m not sure exactly what “add new version” does, but if it is as you mention, that would be helpful.

-dev

#5

I don’t know that you need to “Add a new version” for a plugin. If you’re updating an asset, like an audio pack, it’s a way to let you upload a new .zip file with the content. Plugin updates are managed through the bitbucket repo.

I poked around and didn’t see an “Add new version” field. Can you share a screen shot of that screen?

Rob

#6

That ticket url did the trick - support have been as helpful and responsive as usual this time, and the update is now live =).

Rob, screenshot attached of the menu I see when clicking the cog icon of a product in the products list. It takes you to basically the same page as when editing the listing, but includes a version number field and a “what’s new?” field, both of which populate the right-hand menu of the marketplace page. E.g. https://marketplace.coronalabs.com/corona-plugins/qiso-isometric-tilemap-engine now shows v1.0.1 and a changelog entry.

#7

The “Add a new version” allows you to put in some release notes and a new version number, so people visiting your login page know what’s changed with the plugin. It should not require you to upload a .zip file. Just information.

Rob

#8

Yeah, the other fields all pre-populated with the original info and I didn’t upload a new zip, though the option to was there.

The only way to save those updates though was to submit for approval and apparently a bug in the approval system meant that my submission then disappeared into the matrix. All sorted now :grin: