DetectX | Sqwarq Support: There was a problem verifying your registration details!

“There was a problem verifying your registration details!” Oh no! 😱

Likely you’ve moved all your user files from one machine to another, or perhaps you’ve bought a new Mac or migrated data from a work machine to a personal machine, and now no matter what you do, DetectX just won’t launch. It just keeps spitting out an error message and crashing.

image of problem verifying your registration

Solution:
On the affected machine, go to Terminal and tell DetectX to unregister.

E.g., if DetectX Swift is located in /Applications folder, triple-click the following line of code to select it and copy/paste it into the Terminal window (if the app is located elsewhere, replace “/Applications” with the full path to DetectX Swift’s parent folder). Code:

sudo /Applications/DetectX\ Swift.app/Contents/MacOS/DetectX\ Swift unregister

Press enter and supply an admin password (it’s invisible when you type it).

That should resolve the problem. Try launching the app in the usual way to confirm. If you already have a registration key you should now be able to re-enter it in the usual way.

That Didn’t Work!
If the Terminal returns the error “no such file or directory” or “command not found”, that indicates the path you supplied to DetectX is either incorrect (e.g., it’s not in your Applications folder, it’s somewhere else, like your Utilities folder) or not properly escaped.

What does that mean?
If you examine the command above, you’ll see that immediately after the word “DetectX” is a backwards slash and then a space: DetectX\ . That occurs twice (for both occurrences of “DetectX”).

Ordinarily, the Terminal treats a space as indicating the end of a command or argument, so we need a way to tell it that the command continues after the word “DetectX”. The backward slash is the trick to accomplish this. It “escapes” the space that occurs between the words “DetectX” and “Swift”, effectively telling the Terminal to treat “DetectX Swift” as a continuous string.

Back to your problem: if you’re seeing the error “command not found” then check whether there are any spaces anywhere in the path to DetectX, and if so, make sure you add a backslash right before each space.

sudo <escaped\ path\ to\ detectx> unregister

Note: do not escape the space after sudo or the space before unregister. 🙂

If you’re seeing “no such file or directory” then check that DetectX really is where you’re telling the Terminal that it is. The best way to do this is to type sudo AND a space then drag-and-drop DetectX Swift from the Finder (yes, drop the actual app!) into the Terminal window.

image of detectx registration

Check to see whether the space is escaped or not (if not, escape it), then place the cursor at the end of the word .app (no trailing space) and select, copy and paste the following onto the rest of the line:

/Contents/MacOS/DetectX\ Swift unregister

image of detectx unregister

Press enter and supply an admin password (remember, it’s invisible when you type it) to execute the command.

image of detectx swift has been unregistered

That Still Didn’t Work!!
If you continue to encounter difficulty, then please do the following:

i. Select and copy all the output from Terminal from attempting the above (both your input and the Terminal’s responses) and paste that into an email so I can see what’s going wrong.
ii. Send the email to Sqwarq Support.

🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.