NW Scheduler/Publisher - Updates, Support, and Suggestions

[Cruzer]

4 hours ago, Indapipe said:

My NWP actually just updated to 4.0.10.

 

It appears the NWP update is not available for Apple users yet.

[Tortuga]

4 hours ago, Indapipe said:

My NWP actually just updated to 4.0.10.

Apparently 409 didn't clean things up as well as expected...

[More4me2do]

I updated from 4.0.8 to the latest update for me on Android is 4.0.11 and I am not sure what is happening to the QC of releasing the NWP app. This has never happened before. Upon starting I get the message that there was an error in loading the app. It appeared that everything was successfully loaded except the local data.

 

After a warning for deleting the local data I went through with it. The app now started but everything related to me, like assignments, duties, submitted FS reports and things coming up soon was no longer there. The error log was lengthy. To get the local data back I had to refresh the data under Settings/About and again with a warning.

 

If this happens to other publishers in the congregation, we will be busy. Just my observation but this has never happened in the years we used NWS & NWP. The only explanation I have for this is that there is something rotten in the state of Quality Control before releasing updates.

Edited 20 hours ago by More4me2do

[computerwiz]

An alternative app is starting to look nicer and nicer....  

 

We can't keep having MAJOR hiccups with every MAJOR update.  

[foghorn]

1 hour ago, More4me2do said:

Upon starting I get the message that there was an error in loading the app.

Same here. Kinda unusual: 4.0.10 seemed like it worked fine. Now this... the constant instability is making this app pretty useless right now.

 

MESSAGE TO DEVELOPERS: Here's an idea: once you get everything working again, how about DON'T CHANGE ANYTHING for another 6 months or so! Maybe we have enough advanced clever features... maybe we can just let everyone in the congregation learn to use what is there RIGHT NOW. If this prolonged error phase continues, some congregations will likely pull the plug - we would rather spend hours in the ministry than hours fighting this app!

[More4me2do]

To resolve this problem with 4.0.11 you have to delete the entry in red in the error message that pops up. It warns you but press yes. Upon restarting the app all the entries for your Assignments, Duties, Reports and Upcoming are gone. Open settings then About and click on Refresh Data, ignore any warning.

 

It will repopulate the app with your personal data.

Edited 18 hours ago by More4me2do

[More4me2do]

Wife's phone updated over night and it is a Galaxy S21-5G with Android 15 and it has the loading error. So perhaps some of your publishers will experience this problem after an automatic update. 

Edited 3 hours ago by More4me2do

[Tortuga]

3 hours ago, More4me2do said:

Wife's phone updated over night and it is a Galaxy S21-5G with Android 15 and it has the loading error. So perhaps some of your publishers will experience this problem after an automatic update. 

My phone had the loading error but my tablet and my wife's phone updated without any problem. Thanks for the info.

[Marky]

I am getting the same "Loading Error" message.  Clicking "Reload Local Data" does nothing. If a publisher clicks "DISCONNECT" they will need to login all over again with congregation credentials.  That wil be a nightmare.  What is posted above as a fix is not an option that I can see.  I don't have any other alerts or a way to log out or to refresh anything.

Everything shows Loaded Successfully except Under Persons there is a red Loading Error and a link to click "Delete Local Data."  I am afraid ot click that.

[Marky]

OK - James' fix did work for me.  I read it more carefully. 

FIX: For my Androis, everything showed Loaded Successfully except under Persons there was a red Loading Error and a link to click "Delete Local Data."  I clicked that and a popup appeared - I clicked "Yes" and that restored everything.  

Thanks so much James!

It is going to be a nightmare if we have to instruct all of the publishers how to do this.  Maybe the developers will fix this soon.