NWS Mobile- Beta Testing

[dvdgarofalo]

For those who are currently using/testing the NWS Mobile: How is your experience going? What kinds of issues have you faced? Have you implemented it for the entire share group? Any other observations please share. TYIA

[foghorn]

On 2/8/2026 at 7:42 AM, dvdgarofalo said:

How is your experience going?

Just activated yesterday. Installed on a high-end Samsung Android tablet.

• Install: Had trouble finding NW Scheduler on Google Play Store - had to spell it out completely for some reason
• Activation: simple enough, but notice they now send you a one-time activation code to your email. 
• Normal Startup: Time to sync with congregation data is about same as desktop
• User Interface: Different from Desktop, of course. But very simple and intuitive
• Responsiveness: VERY quick - seems faster than desktop for displaying data
• Usefulness - only 
• Data updating: haven't tried any yet.

[pasher123]

Since we have started using the NWS Mobile, many of the friends have been disconnected from the NW Publisher app. Their name and personal pin are correct, but they receive the following error message "Sorry, this information does not match anyone in this congregation. Please try again or try using CAPITAL LETTERS when entering your First name, or contact your local elders, or tap Help". 

[-Chris-]

• Installed and linked fine on my iPhone.
• UI issues pasting various codes and passwords in on the iPad. I watched another brother type those in without any issue at all on his iPad, was a copy and paste issue. Felt like a problem in whatever UI framework they're using, could make progress by rotating the screen.
• NWS Mobile displays incorrect PINs for publishers, apparently two leading '0' for older 6 digit PINs. These won't work in Publisher.
• A Life and Ministry assignment made on NWS Mobile only partially synced with desktop Scheduler well after the assignment was made. Name field was blank on desktop but Chairman Outline and NWS Publisher showed the brother scheduled. No update at the time for Scheduler. Restart a couple of times resolved it.

[Pastore72]

Hi, I installed it too. One issue I think needs to be fixed is that even if you're not able to see local needs in NWS, you can still see them on the app. Another thing is that when I assign a territory, it would be nice to be able to see the map, otherwise you don't know which one to assign.
What do you think?

[Pastore72]

On 10/02/2026 at 07:23, -Chris- said:

• Installato e collegato correttamente sul mio iPhone.
• Problemi di interfaccia utente quando si incollano vari codici e password sull'iPad. Ho visto un altro fratello digitarli senza problemi sul suo iPad: era un problema di copia e incolla. Sembrava un problema del framework di interfaccia utente che stavano usando, si poteva fare progressi ruotando lo schermo.
• NWS Mobile visualizza PIN errati per gli editori, apparentemente due "0" iniziali per i vecchi PIN a 6 cifre. Questi non funzionano in Publisher.
• Un incarico di Vita e Ministero assegnato su NWS Mobile si è sincronizzato solo parzialmente con lo Scheduler del desktop ben dopo averlo assegnato. Il campo Nome era vuoto sul desktop, ma Chairman Outline e NWS Publisher mostravano il fratello programmato. Nessun aggiornamento al momento per lo Scheduler. Riavviando un paio di volte il problema è stato risolto.

I personally solved the problem by going to NWS, app, people in the NWP app, I select the single publisher and update the person, then I send the data, thus unlocking the single publisher, hello I hope I have been of help to you, best regards

[Pastore72]

On 09/02/2026 at 18:39, pasher123 said:

Da quando abbiamo iniziato a utilizzare NWS Mobile, molti amici sono stati disconnessi dall'app NW Publisher. Il loro nome e il PIN personale sono corretti, ma ricevono il seguente messaggio di errore : "Spiacenti, queste informazioni non corrispondono a nessuno in questa congregazione. Riprova o prova a usare le LETTERE MAIUSCOLE quando inserisci il tuo nome, oppure contatta gli anziani della tua zona o tocca Aiuto". 

if you haven't solved it, I wrote below to the brother who has the same problem

[pasher123]

Creating a new personal pin for the affected publisher seems to solve the issue. There is definitely an issue with the six digit pins.