come on, jasonā¦ thereās light at the end of the tunnel ā¦ (whistling āthereās a light over at the frankānāstein-houseā)
1 Like
Yeah Iām being harsh, but then a portion of the community has had to sit on their thumbs with no backups or device based app-cloud access for a week soā¦ 
Arguably brings in the typical āyouāre welcome to contribute to fix it fasterā statement, but I canāt do thatā¦ so instead focused on topics that come up about it for the last week
this portion should exactly know what it means to work with a betaā¦ itās not meant to be used in a āproductiveā environment. 
Shhhh, donāt bring logic into thisā¦ besides itās an RC 
(and 1.4.3 has SO many more issues for me with uploads, so stuck between a rock and a hard place)
i was simply in sheer despair about 1.4.3. not working at all for me so that i switched to the rc (of course, if microsoft, apple or whoelse is releasing an rc that might mean something, but over here? rc for me would translate as: āsomehow stable betaāā¦ 
)
and my expectations on a working app are quite small: i just want to get my pix uploaded. nutting more- but nutting less, as well. and i know that other ppl have different expectations and needs. so this is clearā¦ ^^
1 Like
Weāre closing in on RC3 with quite some changesā¦ just 3 more PRs to be merged 
Are you saying you donāt expect the same high standards as other industry leaders? How very dare you 
But seriously, I donāt think thatās a perception we should give off - an RC should be 98% stable, last minute call for bugs that the general public (who wouldnāt have touched a dev/beta) will stumble across.
1 Like
it wasnāt me
i agree. and would like to go even farther: RC should be 99,5% stable. but itās always up to the devs how to call their versions. plus: i rather like to test a bit more and longer than the other way round.
1 Like
Tag has been made, @tobiasKaminsky built the release and it has been uploaded to Google Play so it should show up within the next couple of hours
As for your percentage discussion, here are the apps āhard factsā from Google Play:
ANR-free daily sessions
99.5%
Crash-free daily sessions
98.3%
So it is quite stable but if you didnāt nicely updated from 1.4.3 to 2.0.0-rc but installed anything else in between like off-the-grid-test-builds then your database may have been corrupted versioning-wise (which is what we saw in reports). Issue we actually did have is that there was also an error in the db ugrade logic which prevented a clean, fresh installation of 2.0.0RC2 (which is basically the problem since this prevents having a workaround without a new release).
Other issue for sure is that we are currently short staffed as in Mario in vacation and me being swamped at my day job (deputing for other people being on vacation). So one could argue that we shouldnāt have released any RCs. While on the other hand we wouldnāt have found most of the issues that have been reported via Google Playās error reporting except for the DB errors.
So I am truly Sorry for any inconvenience this might have caused you 
but I hope RC3 will work for you 
Published and available according to Google Play 
DOWNLOADING 
sweet, please let us (especially Tobias since he is on duty) know if the release works for you 
hey andy,
for me it is and was all good. no pressure to you guys. i really appreciate your work.
we donāt need to discuss percentages as for me āRCā means ābeta, stillā.
so please donāt waste too much time writing things in here but put your effort elsewhere 
btw: i did an update directly from 1.4.3. to 2.0.0. rc2. with the problems mentioned above (yes, i do run nc 12.0.2)ā¦ thanks for taking them serious.
rock on
jim
1 Like
I can now hit the āenterā key after putting in the server URL
BUT
Instacrash again as soon as permissions are requested. Iāll get logcat shortly.
Ok more feedback:
Iāve seen āapp terminatedā a few times today, far more than on the previous dev builds. Has something changed? Itās killing my large video uploads.
One more bit of feedbackā¦ Iām not sure where itās finding these images, however Iām pretty sure I donāt have 1800+ not already backed up and itās overwriting rather than duplicating if it is indeed re-uploading files.
I let the first 1+ thousand upload a few days ago, so this makes 2800+ itās found to be needing an upload.
Edit - did a rough count, about 1800 pictures all together on the SD card so it is literally duplicating it all.
Not that I know of, cc @tobiasKaminsky @mario
@tobiasKaminsky @mario we also had feedback from another user via the beta programm stating that image folders are shown duplicated in the Auto upload screen which imho shouldnāt be the case. Only thing I can think of is depending on the storage location(s) used by the app (internal, external) in combination with the upload behavior there might be another folder with all these imagesā¦
@tobiasKaminsky @mario I have no clue about this one and would need a stack trace / log to get an idea what happens 
Sorry folks, not around for this one, and you should investigateā¦
The only two reasons for āduplicateā uploads I can imagine:
- duplicate synced folders saved
- something changed timestamp of all the photos
If itās indeed the first, it needs to be fixed. Second sounds very unlikely as I donāt know who/what would do that.
As for video upload crash, well ā¦ dunno? All my tests with the initial APK worked, so Andy, please look into itā¦
for the first time auto-upload somehow works for me with rc3. yay!
butā¦ auto-uploading often fails and needs to be restarted. is thus because of screensaver turning on?
further on i still canāt edit my profile, myself. plus: i canāt even delete it.
and still open as well - deleting a pic from mobile phone doesnāt delete it from NC