More4me2do

First off, there is a difference between restarting and powering off. After closing NWS by either exiting or using Task Manager to force a close, than power down the PC or device. Next start NWS after giving the PC sufficient time to finish starting up. If the identify yourself message doesn't come up than you are authenticated with the server hosting your congregation's data. Speaker sharing is a totally different animal and since we don't use it, I can't help you.

Happened to me also but it only asked me once. That was because I was assigned administrative privileges and I was on my Surface Pro and on the same network as the administrator that assigned it. So, when I came home and opened NWS on my PC it asked me to identify myself while next to the PC the Surface Pro was fine. Entered the Sharing Password and from then on no more asking for identifying.

More inconsistencies or Problems in the NWP app, this time in the Away Speaker details! In the Away Public Talk under Assignments some of the congregations that requested speakers from us DO NOT show the mobile number of the Talk Coordinator who requested the speaker but just his email address. After investigating this further, when the contact number in the NWS app is in the format of (123) 456-7890 it DOES NOT show up it in the NWP app. When it is in the format of 123-456-7890 it DOES display it. For crying out loud, I feel like that this 4.0.* NWP app was released in a beta stage and this will not be the last problem. There are parsing routines for field entries that will check the validity of any entries. The "( )" is a valid entry in the phone field and before you populate the Talk Coordinator details in the NWS app you should run it through a parsing routine and flag it if there are invalid entries or force the entries to a format you want. Since the NWS accepts the (123) 456-7890 format but doesn't display it in the NWP app you must have a problem in the populating of the Talk Coordinator's details in the NWP app. As I mentioned before PLEASE be diligent in the QC before releasing a new version.

I did research and at the present it is possible to run Android apps on a Windows 11 Intel platform. But after reading the needed installation instructions for the Surface Pro 11, I found out that I have to jump through hoops and changes that are not to my liking. The Surface Pro 11 has an ARM 64 processor and because its instruction sets are different then the x86/x64 Intel or AMD processor most of the emulators like BlueStacks can't be installed. The Windows Subsystem for Android is no longer being developed by MS since March 5, 2024. If you want to install it now you need the patched versions found on GitHub. Ever since March 5, 2024 Amazon Appstore was removed from the MS Store which provided the download link. BlueStacks has promised for over a year to provide an Android emulator for the Windows ARM64 platform but has not delivered yet even though many of the Android devices use the ARM64 platform. Thanks for all your help but the NWP app on a windows platform is not recommended by the Devs of the app. https://nwpublisher.com/install-nw-publisher-app-on-windows/

Is there a way to run the New World Publisher app on a Windows 11 Surface Pro 11? I know that Amazon Store is discontinued and there are no entries on the MS Store. Has anyone used an Android Emulator or the Windows Subsystem for Android method to run the NWP app?

So far in the congregation 18 are on version 4.0.11 and the update was done either automatically or manually, Of these 4 had the loading error problem. It seems to be that some phones and tablets don't exhibit this problem after the update.

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.

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.

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.

I don't get the self assigning or the this territory is for this group or family. Our 6 FSGOs and their assistants as well as all the pioneers plus those supporting midweek meetings for Field Service have an understanding and the permission to work in any territory which has blue and orange colored addresses. After all this has a live update of what is being worked. We do campaign and select territories that have not been previously worked during a campaign plus have not been worked recently. The KEY to this is a reliable, dependable and available territory servant who is having his fingers on the pulse of all the territories. Monitoring what FSG needs nearby territory then approaches the FSGO and asks if he needs new territory. He monitors the progress of the territories and if he can determine this one will be overdue, approaches the SO with his findings and a special weekend ministry day by the congregation is arranged to complete overdue territories. This territory module is the most valuable in my opinion as it helps working the territories more thorough, efficient and the results are happy publishers and as they change the status of an address they feel good because they are living up to their dedication vow.

These updates have been FAST & FURIOUS Can we appeal to the QC / QA department to please do a better job of testing as errors are occurring and erroneous messages keep popping up that we have never experienced before. We lost the statuses of territories worked a few weeks before April 25th and today had several times the experience by different publishers, where the householder replied someone was here weeks ago. Not very good optics ….( reduced font size) (edit please don’t yell) we get it you are not happy..no one died..

I open to suggestions for Public Witnessing Schedules. Preferably I like to implement the SMPW way of scheduling. They open the reservation for a month by the 15th of previous month. some take advantage of not having this restriction in place and the earliest one can reserve a slot is July 5th. To sum it up, how do I reserve a key man slot that only key men can reserve and how do I enable the reservations on the 15th of any given month.

From the past when you try to schedule it the software at that time flags it. I keep a separate list of our speakers going out with their talks and the associated revision date and will notify them when they need to address any discrepancies.

That explains it, since I value your input and I am sure many others here do to, perhaps a request from some to take you off the limited access limitation would be very welcome.

I got it, I understand it and I only posted a reply so that others who would draw the same conclusion as I did namely HAVING to tick the radial button YES or NO before they see what you posted in this screen shot. That is not intuitive having to answer something that has no relevance to what you are looking for. A simple explanatory sentence on that page would have solved it or use a drop down text box listing the selecting choices instead of a radial button selection. But it is all good now as we now know how to send our problems and screenshots to the developers.