NW Scheduler/Publisher - Updates, Support, and Suggestions

[Tortuga]

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

 

Edited 23 hours ago by Tortuga

[Indapipe]

2 hours ago, Tortuga said:

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

 

I do see it in my app 4.0.12.

[Tortuga]

1 hour ago, Indapipe said:

I do see it in my app 4.0.12.

Strange. It's been missing through several updates for us.

[carlos]

13 hours ago, Matt S said:

The congregation PIN is used to encrypt your congregation data. If the congregation changes the App PIN, the publishers needs to reconnect using the new congregation PIN, otherwise their phones won't be able to decrypt the data. This publisher hasn't reconnected with the new congregation PIN since your congregation last changed the App PIN. Once they reconnect with the congregation's new PIN their device will be able to decrypt the data again.

 

Thanks, Matthew. This comment is useful.

 

A suggestion: If a message like "The PIN number entered is incorrect" were included in the error message, it would be easier to understand what the issue is. 

 

6 hours ago, Tortuga said:

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

It's happening to us too. 

[Matt S]

6 hours ago, Tortuga said:

The recent NWS and NWP have not fixed the problem with the Publisher Person PIN in NWP. The field is still empty for everyone. Is anyone else having that problem?

 

 

3 hours ago, Indapipe said:

I do see it in my app 4.0.12.

 

2 hours ago, Tortuga said:

Strange. It's been missing through several updates for us.

 

It's not a problem with NWP. You just need to refresh the app data, in your case it would be Persons app data.

 

[Tortuga]

54 minutes ago, Matt S said:

 

 

 

It's not a problem with NWP. You just need to refresh the app data, in your case it would be Persons app data.

 

Do you mean the NWS Admin needs to refresh the app data? 

I have refreshed my NWP app data and it didn't help.

[Tortuga]

The last update radically changed the was the cleaning assignments are displayed in NWP.

 

We schedule the cleaning assignments per meeting in NWS but this is what NWP shows now.

[Matt S]

25 minutes ago, Tortuga said:

Do you mean the NWS Admin needs to refresh the app data? 

I have refreshed my NWP app data and it didn't help.

 

It is not a person by person thing. The instructions in the screenshot I previously posted need to be followed from NWS, not in NWP. The person doing the data refresh would likely need edit access to that data type.

[More4me2do]

18 hours ago, Matt S said:

 

You said you haven't enabled NWS Mobile, and yet a publisher has this problem, so the problem isn't caused by NWS mobile. This screenshot is from NW Publisher, which is unrelated to NWS Mobile.

 

The congregation PIN is used to encrypt your congregation data. If the congregation changes the App PIN, the publishers needs to reconnect using the new congregation PIN, otherwise their phones won't be able to decrypt the data. This publisher hasn't reconnected with the new congregation PIN since your congregation last changed the App PIN. Once they reconnect with the congregation's new PIN their device will be able to decrypt the data again.

 

I get what you are saying but you didn't follow my reaasoning. I know it has nothing to do with Mobile and it is obvious that this screenshot is from NWP.

 

NO pins were changed!!! Out of the blue this error message appeared on an iPhone and it is the first. What you suggested of disconnecting and reconnecting should fix it, but why did this happen in the first place when nothing but updates were happening? Add to that the previous loading error which only could be solved by deleting the local data.

 

So something is not quiet correct in the updates and feature roll out.

 

Now the Mobile feature addition. As long as you stay in the Windows world things are sort of stable in that OS. Now you add the iOS and Android OS to that. It is my understanding that to make these 3 OSs work the encryption had to be changed which in turn effected the decryption. Going by the past record of the major updates, it easier for me to believe that this introduced an error because what else could could have caused it when nothing else was changed?

 

Here is the verification for what I assumed:

Yes. In version 8.1, NW Scheduler upgraded its End-to-End (E2E) encryption algorithms across NWS Desktop, NWS Mobile, and the NWP app to Argon2id + AES-GCM with AAD

 

More likely for me to believe that this is where problem lies.

Edited 12 hours ago by More4me2do

[More4me2do]

4 hours ago, Tortuga said:

Do you mean the NWS Admin needs to refresh the app data? 

I have refreshed my NWP app data and it didn't help.

 

I just had to do this for territories because lots of data was missing like territories that showed in NWS as not completed but were not showing up in the NWP. Go the App section (the icon that looks like phone) on the right side under App Administration select Refresh Selected App Data and from the drop down box select what data you want to refresh.

 

Then after initiating this you get a bunch of warnings do you really want to do this and click yes. It will put the data in the Send App Data box. Go to that box and you will see all the entries of the data that will be resent. Click send.

 

In my case all the missing territory data reappeared.

[Tortuga]

Just now, More4me2do said:

 

I just had to do this for territories because lots of data was missing like territories that showed in NWS as not completed but were not showing up in the NWP. Go the App section (the icon that looks like phone) on the right side under App Administration select Refresh Selected App Data and from the drop down box select what data you want to refresh.

 

Then after initiating this you get a bunch of warnings do you really want to do this and click yes. It will put the data in the Send App Data box. Go to that box and you will see all the entries of the data that will be resent. Click send.

 

In my case all the missing territory data reappeared.

Thanks. I am in View Only mode so I can't do any of that but I shared the information with the Secretary and he will do it. It's hard for me to poke around and figure out what he needs to do because I can't access all of the information. Thanks for the help.

[More4me2do]

20 minutes ago, Tortuga said:

Thanks. I am in View Only mode so I can't do any of that but I shared the information with the Secretary and he will do it. It's hard for me to poke around and figure out what he needs to do because I can't access all of the information. Thanks for the help.

When you are in view mode only you will not be able to see what is in the drop down box, which means what selective refresh areas are available.

[Floyd]

7 hours ago, More4me2do said:

 

I get what you are saying but you didn't follow my reaasoning. I know it has nothing to do with Mobile and it is obvious that this screenshot is from NWP.

 

I get the confusion though because the first thing you said was related to NWS Mobile. Therefore I thought he screenshot was from NWS Mobile. It was not obvious to me that the screenshot was from NWP. 

[More4me2do]

1 hour ago, Floyd said:

 

I get the confusion though because the first thing you said was related to NWS Mobile. Therefore I thought he screenshot was from NWS Mobile. It was not obvious to me that the screenshot was from NWP. 

 

Sorry, if that was not clear, but I thought the message itself "ask your local elders tp refresh selected app data" would indicate that this is relating to data sent from NWS to NWP because it is a decrypting error. Or the three error subheadings "Congregation", "App settings", "Territory Settings" would not appear in NWS but in NWP because it is "APP".

Perhaps I was too engaged that this error was a result of the change in the End-To-End encryption in all three programs. The odds heavily favor that this is the case since nothing changed on the person's device except NWP updates and I am on top of NWS. 

[Floyd]

15 minutes ago, More4me2do said:

Or the three error subheadings "Congregation", "App settings", "Territory Settings" would not appear in NWS but in NWP because it is "APP".

 

NWS Mobile is also an "APP" which also has "Congregation" and "App settings." True NWS Mobile does not have territory settings.

I am the admin for NWS and nobody in our congregation has experienced what you have experienced. I would say what you have have experienced with this error is out of the ordinary. Be careful about telling people to "Get the basics right and flawless." None of us are perfect and out of the ordinary things are bound to happen. 

"Take a screenshot of this error and send to your local elders" is the right thing to do since really it should be the admin who contacts support.

Getting angry about something is not going to accomplish anything even in dealing with worldly companies. The goal is to fix the problem. You can test complex programs 1000's of times and still somebody will find a problem with it eventually. It happens all the time. This time you were the one who found a problem.

[More4me2do]

11 minutes ago, Floyd said:

I am the admin for NWS and nobody in our congregation has experienced what you have experienced. I would say what you have have experienced with this error is out of the ordinary. Be careful about telling people to "Get the basics right and flawless." None of us are perfect and out of the ordinary things are bound to happen. 

 

Normally I would agree with that but since the 8.1 version's release the updates to correct errors has been fast and furious. The track record since that change has been worst then all the updates before. This thread is filled with difficulties that were basic and should have been caught before release. But I can't shake the feeling that there is a rush to release a Mobile version as very few live in the Windows world. I shelled out $1,200 for a Surface Pro 11 just so that I have portable NWS and most likely not all can afford that. The complexity of NWS will become massive because now you will have to test and check two versions of NWS and how changes will effect this Eco system.

[Floyd]

4 minutes ago, More4me2do said:

 

Normally I would agree with that but since the 8.1 version's release the updates to correct errors has been fast and furious. 

 

I had the opposite experience. Previously I had big problems with major updates. This time I followed the instructions exactly. I immediately sent a text to all the brothers and told them to not update until I told them to. I waited several days for more updates to come out then I updated and checked everything. Then I told the other brothers to update. Very few problems after that. Very smooth. I don't think I am out of the ordinary. The are many congregations in my area who use NWS and we talk to each other and we have all had a similar experience. Yes there are a lot of comments on this thread about problems but that is hardly a majority. At best it's anecdotal. 

[Pastore72]

15 ore fa, Tortuga ha detto:

L'ultimo aggiornamento ha cambiato radicalmente le assegnazioni di pulizia visualizzate in NWP.

 

Pianifichiamo gli incarichi di pulizia per riunione in NWS, ma questo è ciò che NWP mostra ora.

 

Hi everyone, we're having the same problem after the update. Honestly, we're a little tired of all these bugs. Every update brings new errors and data loss. Even though we back up daily, restoring often doesn't fix it. I'm sorry, because the previous version worked without any major problems, and we were very happy to have switched to this hourglass program.
We hope they fix it soon.... Best regards from Italy (I think I'm the only one on this forum).