I've been fixing it manually by adding 7.2.5 support to the file. Otherwise, release builds that are tagged through source control don't appear to be automatically pushing to Curse and Twitch.
i usually upload my zip releases first as Alpha versions, wait for them to be synced to the app, test how they update and if the checksums of the files are preserved (because Curse has a history of altering the files inside the uploaded zip file) and only then after these tests i edit the uploaded file and change the type from Alpha to Release.
Today i noticed that the following warning has appeared on the file upload page so i had to upload my zip file as Beta instead.
Alpha files will not sync to the Twitch Desktop app or mods.curse.com.
It seems that Alpha versions are terminated from the Twitch App as addon sync of alpha versions has been permanently stopped.
They will probably remove soon the "Alpha" addon version option from the App too - it's still there but apparently it now does the same thing as "Beta".
@Adrian_G2 That has always been true, and nothing has been changed. Alpha build addons have never by default propagated to either the client or curse.com. End users can set addons individually or en masse to install alpha builds in the client if they so choose.
Beta and release addons have always propagated to curse.com and the client, again no change. Therefore I am confused what you think has changed.
well, i don't remember ever seeing that notification text before the sync hiccups started to happen at the end of August. I saw it today and i thought it was something that was changed recently due to the issues.
I think that Curse's notification text is pretty clearly intended to mean Alphas will never sync, no matter what settings the user makes in the client app. That notification text does not leave room for any user choice in this matter, so.. *headscratch*. Maybe it's a translation issue?
Also, DBM is still publishing alpha updates and they arrived via the app even today, so i was puzzled there.. why are some alphas still synced even with that notification there?
The notification was added recently because we have been inundated with support tickets from people who have projects (primarily in Minecraft) which only contain Alpha files; such projects will not sync to the App at all. Projects will only sync to the App when there is at least one Release file, since installation of Alpha and Beta files is an opt-in scenario - otherwise, there would be hundreds of seemingly empty projects showing up in the App since the majority of users do not opt-in for anything other than Release files.
The message could be more clear on this, certainly, but it immediately points out to people that if they want people to actually use the project they need to do more than upload Alpha versions.
Ah yes DBM (and other addons) that are set to alpha builds. Okay, here's what's going on: when you set the release type to Alpha as per your picture above, then files on DBM's project page (Curseforge) will show some alpha builds. That does not mean those alpha builds are going to Curse or the Twitch app.
All this does is provide a way for an addon author to create zip files of alpha builds. If the author switches to Beta, then alpha builds will not be zipped up. If the author toggles Release, then only Release builds will be zipped and available as downloads.
This is true for both Curseforge and Wowace, and it is not unique to DBM; any project on either Curseforge or Wowace can be set to the preference of the addon author.
Which, as an opinion, bugs me that the author allows alpha builds as zips because then I get "your version is out of date" messages when I join groups and raids, when in reality, while technically true, the author is still making changes and DBM is not ready for the masses. But that is just me.
it's almost 24 hours now since i uploaded a new zip release (it was approved), made changes to the overview description page and uploaded new screenshot images so that the description and the images match the current release.
none of these changes have been synced to curse.com (or the app) yet. :(
edit: it has now been synced. What was the size of the boot that was needed to kick it into action? :p /s
We're seeing a similar issue with the Raider.IO addon. Since it sounds like some here are saying it is fixed for them, I wanted to reach out to bring it up that our situation does not appear fixed.
Currently our addon https://wow.curseforge.com/projects/raiderio shows as having the latest release from 2 days ago. However we've been pushing a tagged commit once to twice per day to github, and have had a webhook setup to send this to CurseForge for packaging. In the CurseForge Dashboard I can see that the hooks have been received from github, but the recent calls don't attempt to package a build.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI also have that issue with my Addon (new version not showing up on curse.com):
https://wow.curseforge.com/projects/xpflag
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis seems resolved now.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLooks like it's doing it again. I tagged a new version and it's been over 24 hours and it still doesn't show as updated.
https://mods.curse.com/addons/wow/gtfo
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator@Zensuim looks like GTFO is fixed. The same version is on Curse, Curseforge, and the Twitch app: 4.43.2.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI've been fixing it manually by adding 7.2.5 support to the file. Otherwise, release builds that are tagged through source control don't appear to be automatically pushing to Curse and Twitch.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumi usually upload my zip releases first as Alpha versions, wait for them to be synced to the app, test how they update and if the checksums of the files are preserved (because Curse has a history of altering the files inside the uploaded zip file) and only then after these tests i edit the uploaded file and change the type from Alpha to Release.
Today i noticed that the following warning has appeared on the file upload page so i had to upload my zip file as Beta instead.
Alpha files will not sync to the Twitch Desktop app or mods.curse.com.
It seems that Alpha versions are terminated from the Twitch App as addon sync of alpha versions has been permanently stopped.
They will probably remove soon the "Alpha" addon version option from the App too - it's still there but apparently it now does the same thing as "Beta".
-
View User Profile
-
View Posts
-
Send Message
Forum Moderator@Adrian_G2 That has always been true, and nothing has been changed. Alpha build addons have never by default propagated to either the client or curse.com. End users can set addons individually or en masse to install alpha builds in the client if they so choose.
Beta and release addons have always propagated to curse.com and the client, again no change. Therefore I am confused what you think has changed.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumwell, i don't remember ever seeing that notification text before the sync hiccups started to happen at the end of August. I saw it today and i thought it was something that was changed recently due to the issues.
I think that Curse's notification text is pretty clearly intended to mean Alphas will never sync, no matter what settings the user makes in the client app. That notification text does not leave room for any user choice in this matter, so.. *headscratch*. Maybe it's a translation issue?
Also, DBM is still publishing alpha updates and they arrived via the app even today, so i was puzzled there.. why are some alphas still synced even with that notification there?
-
View User Profile
-
View Posts
-
Send Message
AdminThe notification was added recently because we have been inundated with support tickets from people who have projects (primarily in Minecraft) which only contain Alpha files; such projects will not sync to the App at all. Projects will only sync to the App when there is at least one Release file, since installation of Alpha and Beta files is an opt-in scenario - otherwise, there would be hundreds of seemingly empty projects showing up in the App since the majority of users do not opt-in for anything other than Release files.
The message could be more clear on this, certainly, but it immediately points out to people that if they want people to actually use the project they need to do more than upload Alpha versions.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorAh yes DBM (and other addons) that are set to alpha builds. Okay, here's what's going on: when you set the release type to Alpha as per your picture above, then files on DBM's project page (Curseforge) will show some alpha builds. That does not mean those alpha builds are going to Curse or the Twitch app.
All this does is provide a way for an addon author to create zip files of alpha builds. If the author switches to Beta, then alpha builds will not be zipped up. If the author toggles Release, then only Release builds will be zipped and available as downloads.
This is true for both Curseforge and Wowace, and it is not unique to DBM; any project on either Curseforge or Wowace can be set to the preference of the addon author.
Which, as an opinion, bugs me that the author allows alpha builds as zips because then I get "your version is out of date" messages when I join groups and raids, when in reality, while technically true, the author is still making changes and DBM is not ready for the masses. But that is just me.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIs it normal for an update to still be processing after 2 hours? There's no md5 hash generated?
-
View User Profile
-
View Posts
-
Send Message
AdminThere was an issue with the file processors - is this still happening for your project? If so, please give me the URL here and I'll kick-start it.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIn reply to Torhal:
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttps://mods.curse.com/addons/wow/o-item-level
does not push update to curse.com though in curseforge v6.7.18 was approved
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumhttps://wow.curseforge.com/projects/auctioneer-cheapo-searcher-module-with-transmog
it's almost 24 hours now since i uploaded a new zip release (it was approved), made changes to the overview description page and uploaded new screenshot images so that the description and the images match the current release.
none of these changes have been synced to curse.com (or the app) yet. :(
edit: it has now been synced. What was the size of the boot that was needed to kick it into action? :p /s
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI have a small question. When do under review files start getting processed in the day? Is there a set schedule? It would be nice to know.
-
View User Profile
-
View Posts
-
Send Message
AdminAt the moment, we're only covering 16 hours per day for logistical reasons. This was announced here: https://www.curseforge.com/news/3000-time-to-break-the-silence-new-community-efforts
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIn reply to Torhal:
We're seeing a similar issue with the Raider.IO addon. Since it sounds like some here are saying it is fixed for them, I wanted to reach out to bring it up that our situation does not appear fixed.
Currently our addon https://wow.curseforge.com/projects/raiderio shows as having the latest release from 2 days ago. However we've been pushing a tagged commit once to twice per day to github, and have had a webhook setup to send this to CurseForge for packaging. In the CurseForge Dashboard I can see that the hooks have been received from github, but the recent calls don't attempt to package a build.
All these commits have been tagged.
Thanks for any assistance you can provide.
Problem solved