Skip to main content
Accessibility Resource Center Skip to main content
Get up to $500 when you bring your phone. Plus, waived smartphone activation fee when you buy online. Limited time offer.
end of navigation menu
cancel
Showing results for 
Search instead for 
Did you mean: 
Re: MESSAGE+. ERASE and RECONNECT message
aweisbach1957
Member

Not really sure who you are replying to - me or the last person to chime in. As I stated before, I used to run the app on my android phone, my PC laptop, and my MAC but it stopped working properly on the MAC so I uninstalled it. Now, if I try to reinstall I get stuck at the "erase & reconnect" message.

As others have indicated, the bottom line seems to be that when the app is "uninstalled" from a MAC it really is NOT completely uninstalled, and we need to know what to do on the MAC to actually get it completely uninstalled, so it can then be re-installed. 

In PC terms it's like there are remaining references to the app in the Registry that need to be deleted. But MACs don't have a registry, so what needs to be done to make it like it was never, ever, installed on a MAC?

0 Likes
Re: MESSAGE+. ERASE and RECONNECT message
jrmihalick
Member

I am having the exact same problem on a Mac Mini (with macOS Mojave 10.14.5) running the latest version of Verizon Message+ 2.5.2.  Once I choose to erase and reconnect, I get the attached message indefinitely.  I have let it run for 24 hours and it never goes away.

Screen Shot 2019-08-10 at 7.08.05 AM.png

Here also are the messages I am seeing in the macOS system logs.  Note the message in bold red below. I wonder if this is the root cause.

default 07:10:45.839022 -0400 Message+ Current system appearance, (HLTB: 1), (SLS: 0)
default 07:10:45.841918 -0400 Message+ Post-registration system appearance: (HLTB: 1)
default 07:10:45.858819 -0400 Message+ NSApp cache appearance:
-NSRequiresAquaSystemAppearance: 1
-appearance: (null)
-effectiveAppearance: <NSCompositeAppearance: 0x600001948cd0
(
"<NSAquaAppearance: 0x600002f71d40>",
"<NSSystemAppearance: 0x600002f71b40>"
)>
error 07:10:46.019521 -0400 Message+ AEGetDescData of non-desc type 'reco' not a good idea
default 07:10:46.029945 -0400 Message+ [Crashlytics] Version 3.8.3 (120)
default 07:10:46.035169 -0400 Message+ Task <76253B6C-2CF0-40DF-B631-23E648550179>.<1> resuming, QOS(0x21)
default 07:10:46.038594 -0400 Message+ Faulting in NSHTTPCookieStorage singleton
default 07:10:46.038609 -0400 Message+ Faulting in CFHTTPCookieStorage singleton
default 07:10:46.038618 -0400 Message+ Creating default cookie storage with default identifier
default 07:10:46.038915 -0400 Message+ Task <76253B6C-2CF0-40DF-B631-23E648550179>.<1> {strength 0, tls 4, ct 0, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default 07:10:46.039429 -0400 Message+ TIC Enabling TLS [1:0x600000f430c0]
default 07:10:46.039631 -0400 Message+ TIC TCP Conn Start [1:0x600000f430c0]
default 07:10:46.039785 -0400 Message+ [C1 Hostname#5bc66522:443 tcp, url hash: cd77df8c, tls] start
default 07:10:46.040149 -0400 Message+ nw_connection_report_state_with_handler_locked [C1] reporting state preparing
default 07:10:46.040978 -0400 Message+ Task <76253B6C-2CF0-40DF-B631-23E648550179>.<1> setting up Connection 1
default 07:10:46.056677 -0400 Message+ Task <84277292-E25C-47B5-AD33-2F66B5497F64>.<1> resuming, QOS(0x9)
default 07:10:46.061345 -0400 Message+ Task <84277292-E25C-47B5-AD33-2F66B5497F64>.<1> {strength 0, tls 4, ct 0, sub 0, sig 1, ciphers 0, bundle 0, builtin 0}
default 07:10:46.061503 -0400 Message+ TIC Enabling TLS [2:0x600000f5e1c0]
default 07:10:46.061527 -0400 Message+ TIC TCP Conn Start [2:0x600000f5e1c0]
default 07:10:46.061720 -0400 Message+ [C2 Hostname#a6c0f34e:443 tcp, url hash: 54e04379, tls] start
default 07:10:46.062225 -0400 Message+ nw_connection_report_state_with_handler_locked [C2] reporting state preparing
default 07:10:46.062836 -0400 Message+ Task <84277292-E25C-47B5-AD33-2F66B5497F64>.<1> setting up Connection 2
default 07:10:46.098988 -0400 Message+ nw_socket_handle_socket_event [C1.1:3] Socket received CONNECTED event
default 07:10:46.099115 -0400 Message+ nw_endpoint_flow_protocol_connected [C1.1 IPv4#7cb4aa6f:443 in_progress socket-flow (satisfied)] Transport protocol connected
default 07:10:46.103367 -0400 Message+ TIC TLS Event [1:0x600000f430c0]: 1, Pending(0)
default 07:10:46.133474 -0400 Message+ nw_socket_handle_socket_event [C2.1:3] Socket received CONNECTED event
default 07:10:46.134006 -0400 Message+ nw_endpoint_flow_protocol_connected [C2.1 IPv4#14e267f9:443 in_progress socket-flow (satisfied)] Transport protocol connected

---------- 8< ------------------------ snip ---------------------------------------- 8< -------------------

default 07:10:51.330366 -0400 Message+ 0.000s [C9 <private> Hostname#10884595:443 resolver] path:start
default 07:10:51.330389 -0400 Message+ 0.000s [C9 <private> Hostname#10884595:443 resolver] path:satisfied
default 07:10:51.330411 -0400 Message+ 0.000s [C9 <private> Hostname#10884595:443 resolver] resolver:start_dns
default 07:10:51.330432 -0400 Message+ 0.001s [C9 <private> Hostname#10884595:443 resolver] resolver:receive_dns
default 07:10:51.330458 -0400 Message+ 0.001s [C9.1 <private> 192.168.1.100:64088<->IPv4#fde938a8:443 socket-flow] path:start
default 07:10:51.330480 -0400 Message+ 0.001s [C9.1 <private> 192.168.1.100:64088<->IPv4#fde938a8:443 socket-flow] path:satisfied
default 07:10:51.330504 -0400 Message+ 0.002s [C9.1 <private> 192.168.1.100:64088<->IPv4#fde938a8:443 socket-flow] flow:start_connect
default 07:10:51.330527 -0400 Message+ 0.073s [C9.1 <private> 192.168.1.100:64088<->IPv4#fde938a8:443 socket-flow] flow:finish_transport
default 07:10:51.330581 -0400 Message+ 0.073s [C9 <private> Hostname#10884595:443 resolver] flow:finish_transport
default 07:10:51.330686 -0400 Message+ 0.146s [C9.1 <private> 192.168.1.100:64088<->IPv4#fde938a8:443 socket-flow] flow:finish_connect
default 07:10:51.330721 -0400 Message+ 0.146s [C9 <private> Hostname#10884595:443 resolver] flow:finish_connect
default 07:10:51.330761 -0400 Message+ 0.146s [C9.1 <private> 192.168.1.100:64088<->IPv4#fde938a8:443 socket-flow] flow:changed_viability
default 07:10:51.330783 -0400 Message+ 0.146s [C9 <private> Hostname#10884595:443 resolver] flow:changed_viability
default 07:10:51.330895 -0400 Message+ 0.221s [C9] path:cancel
default 07:10:51.331532 -0400 Message+ nw_endpoint_flow_protocol_disconnected [C9.1 IPv4#fde938a8:443 cancelled socket-flow (null)] Output protocol disconnected
default 07:10:51.331670 -0400 Message+ nw_connection_report_state_with_handler_locked [C9] reporting state cancelled
default 07:10:51.331709 -0400 Message+ Task <579855FD-93BE-4D73-8797-41993DDCAF69>.<0> done using Connection 9
default 07:10:51.331752 -0400 Message+ TIC TCP Conn Destroyed [9:0x600000f35800]
default 07:10:55.929618 -0400 Message+ LSExceptions shared instance invalidated for timeout.

default 07:10:56.483522 -0400 Message+ [Accounts] Failed to update account with identifier F6BE1931-26EC-49C9-AF1A-11DBC7649168, error: Error Domain=ABAddressBookErrorDomain Code=1002 "(null)"

0 Likes
Re: MESSAGE+. ERASE and RECONNECT message
QBOY61
Member

I am working on my wife's computer and the Message+ app is not recovering from "Disconnecting device & erasing data...".  With this last uninstall/reinstall I removed the Mac device on the VerizonWireless Text web page settings which caused the problem.  Previous to this last reinstallation, I've thrown the icon in the trash twice and the application comes back after reinstall and all the configurations are there as if the application was not removed.  Obviously the uninstall is NOT removing the entire application and that will not clear the issues that my wife is having on her Mac (I'd imagine there are some "bad" messages causing issues).  And removing the device causes the application to fail at removing the old data.  Someone at Verizon needs to help us manually remove the hidden database on MacOS.

0 Likes
Re: MESSAGE+. ERASE and RECONNECT message
vzw_customer_support
Customer Support

We are sorry to hear of the issue you are having with Message+ QBOY61. Since you are indicating that you need to manually remove the hidden database, you will want to work with Apple directly. https://support.apple.com/

RosanneM_VZW

0 Likes
Re: MESSAGE+. ERASE and RECONNECT message
Icanthearu
Member

I have the same issue, with Message+ running properly on one Mac with OS x 10.15 Catalina, but it refuses to Erase and Reconnect on a Mac running OS X 10.13.6 High Sierra.

I am runnig the same version,  Version 2.5.2 (2.5.2), on both machines.

Here is what people think of Message+ and you can thank Verizon Support for their *contributions*.

 

Message+ ratings.png

 

 

 

 

With all possible due respect, telling anyone to *work directly with Apple* to manually remove an unknown data base is blatant garbage. The database is unknown because Verizon won't say what or where it is. I have Terminal access and can, if necessary, delete any file, including critical system files......BUT TO DO THAT I NEED TO KNOW THE NAME OF THE FILE AND WHERE THE HECK IT IS.

I am technically capable of doing this at ROOT, but I NEED TO KNOW THE NAME OF THE FILE(s) AND WHERE THE HECK IT(they) IS (are).

Message+ is a Verizon App. Is Verizon now saying they not only don't know what files their app writes, it doesn't even know where they are???

Where is the hidden database and what is its name???? Or is Verizon expecting me to call Apple and say, "Hi, I need to remove a hidden database that Verizon Message+ uses. How do I do that?"

Does Verizon have some agreement with Apple to support Verizon's app??

If not, I can tell you right now where Apple is going to send me.......right back to YOU.

Re: MESSAGE+. ERASE and RECONNECT message
Icanthearu
Member

After my rant Man Frustrated , I did some legwork and found, what I think is a fix. Man Wink

As earier noted, the problem is, Messager+ is not fully deleting, but Verizon can't seem to say how to go about fully deleting it. I had tried Spotlight and other ways of finding these files to no avail. So I got to searching and found a free utility that pulls up all the files associated with an App. AppCleaner AppCleaner opens into a window where you drag the app you want to delete. It finds them all. Some were checked, some were not. I checked them all and hit Delete. Admin password is required.

After the deletion, I Emptied the trash, just to be sure. Then went to AppStore and reinstalled Message+. Opened with no problems and is currently running properly on both Macs.

AppCleaner is a pretty cool little app. I'm adding it to my must have software.Heart

Re: MESSAGE+. ERASE and RECONNECT message
Icanthearu
Member

On more thing. Just in case someone is curious or just wants to manually delete them. Here are the files found to be associated with Message+ by AppCleaner. As you can see, some are checked, some are not. I checked and deleted them all. So far, I see no negative impact from that action.

 

Message+ files.png

Re: MESSAGE+. ERASE and RECONNECT message
jrmihalick
Member

I can confirm that manually removing the above files and then re-installing the Message+ application from the App Store  also works!  Thanks for posting the solution @Icanthearu  ! 

You have done what all of the Verizon support associates (and there have been many of them that replied on this thread), who have access to the actual software developers that wrote the application, were unwilling to do, and that is research and not give up until you found a solution.  Verizon should credit you with a few months of service for this because you have saved who knows how many folks that follow a ton of frustration.

0 Likes
Re: MESSAGE+. ERASE and RECONNECT message
Icanthearu
Member

Thanks jrmihalick

ONE MORE THING for anyone else out there.

Do not delete com.verizon.vzmessagesmac.savedState which is in your home Library. I did and Messages+ would not recognize that I had previously logged in. (irritating) Man Frustrated I was having to "Start messaging" every time I started the App until I figured out that file was missing and how to recreate it.

Uninstalling and reinstalling Message+ would not replace the file for me (Mac OS x 10.13.6 High Sierra) and it could vary by OS.

To do the following, you'll need to make *hidden* items visible as the files and folders you need are normally hidden. Hidden files and folders are hidden for a good reason. If you don't know what you're doing, call Apple and have them walk you through it. I believe all you actually *have to do* is create an alias of com.verizon.vzmessagesmac which is in ~/Library/Application Scripts, then drag that alias to ~/Library/Saved Application State and change its name  to  com.verizon.vzmessagesmac.savedState. I have some hesitation doing it this way as you end up with an alias that has permission groups and a *folder* icon. This is different in that the original one did not had no permissions group and a generic icon. While I ran into no problems using it, something *might* pop up later so I worked with it until I had pretty much what appears to be an exact duplicate of the alias... 'cause I wanted it that way.

The Icon and Permissions group things can be fixed, using a couple of creative work arounds, but if no one is having any problems, I'll leave it at that. Feel free to PM me, if needed.

To make hidden files visible, see https://www.wikihow.com/Show-Hidden-Files-and-Folders-on-a-Mac

0 Likes
Re: MESSAGE+. ERASE and RECONNECT message
vzw_customer_support
Customer Support

Jrmihalick, we're glad the steps icanthearu helps. I will ensure to submit your feedback, as your voice matters, and it's never our goal for our customers to feel this way after working with us.

 

ChakiaH_VZW

0 Likes