First of all, many thanks for this incredible app.
I have some doubts regarding sequential updates on a ROM.
I've build a ROM without OTA Updater. Afterwards, I've added the OTA Updater through a flashable zip and delivered it to anyone who wants to use my ROM with the OTA Updater feature. So far so good.
I've made the first update to the ROM (a simple update) just to test if the OTA Updater works. It did work but I've noticed that I'm only able to launch updates if I perform an update to the ROM itself on your database instead of adding a new entry.
Meaning, I had a zip on your database with a name and an id. I had to replace that zip for another in order to maintain the ROM's name and id, the only things that changed were the date and version.
I though I could add another ROM entry with the same name and id but with different version and build date (since you've stated on the OP that "For further updates, just make sure you update the otatime and otaver properties in build.prop"). That operation resulted with "ERROR", no more no less.
And so, if I got his correctly, all other future updatable zips I'll release, will have to include the previous modifications, right?
Either that, or I'll have to change the ROM's name and/or id every time I release an update. That will be confusing...how do I edit the build.prop correctly in order to "tell" your database that a new version exists, since the id and/or name will be different?
I hope you may understand what I'm talking about. Since it may be confusing while reading.
Thanks in advance!