Appears Buggy

Hi Judy,

Sorry to hear this! I am trying to work out what might have happened here. Looking in our logs, I can see that:

– You created an account 13 days ago, and connected a site (log timestamp: 29/Jun/2017:23:53:44 GMT).

– This review was posted on 12 Jul, at 01:27 GMT (according to “X hours, Y minutes ago” calculation).

– 14 minutes after that, your app sent a “delete site” command (12/Jul/2017:00:41:42).

– Then 23 minutes later, a new “add site” command (12/Jul/2017:01:04:06).

From that flow, I’m trying to work out exactly what went wrong. It seems that the site was still in the account at the time of the review, and then deleted. So, the problem that triggered the error was not that the site vanished from the account – it is something else. I am going to ask our iOS app developer to have a look at this, in case he has some suggestions, or if it is a known issue with the version of the iOS app that you have (1.2.3).

David

Hi Judy,

Having looked further through the logs, I believe that:

1) This is due to a bug in the current iOS app, which is fixed in the next update, which is waiting for Apple to clear it.

2) If you make sure that you visit your login URL over https:// and not over https:// then it will work, even before that next update.

I am just waiting to clarify this with our lead iOS developer, who is currently out to lunch.

David

Hi Judy,

OK – he’s confirmed that this is a bug. There’s a new 1.2.4 release that should be out around now, but the fix is in 1.2.5, which Apple will hopefully have approved for release by Friday. Until then, you will want to make sure that you visit your login URL over https://, not https:// . And then after that (once you’ve got the update), it should not matter.

David

It is broke again. I got in with Keyy. However, I then activated the HTTPS feature in the SG Optimizer plug in to redirect all traffic to the HTTPS site. Now Keyy is not working. Also, the URL to login in without Keyy is not working either. So I am not able to get into my site admin panel. My opinion of Keyy is not improving.

Hi Judy,

I can see that as a result of that, the problem is now the other way round… this time, you scanned the code to connect whilst logged in to your WP dashboard over http, but now with the new plugin, the login page is only available over https. (Before, you logged into your dashboard over https, and then were having problems with the login page over http). So, the mismatch is still there (i.e. same problem).

I have adjusted your account so that it now sees the site as being https. However, it is necessary for the app to be told to re-pull the information from your account. I do not have an iOS device and our iOS people have gone home for the day. I think that one of these three alternatives should do it:

1) I think that there is an option on the app menu to ‘refresh’ – i.e. pull your account details down again.

2) Or, there may be an option in the app to edit the site URL – you could use that to change the https:// to https:// . (There is in Android, so I think it should be in iOS too).

3) Or, if you connect a second WP site, then this will automatically cause a refresh.

Alternatively, as I mentioned before, this issue (that the iOS app has trouble if you connect over http and then login over https, or vice-versa), is fixed in our current development version, and is just waiting on Apple’s approval process to get out to everyone. This is version 1.2.5. Based on their normal approval times, we anticipate it should be out there by Friday.

The “disable Keyy URL” is a one-time URL, because of its security importance. Hence, after you use it, you need to re-visit the admin page and get the new one, as the old one cannot be re-used. (This is also emailed to the site admin when it is refreshed – so, you could check your spam folders).

You can also entirely disable Keyy by putting this in wp-config.php (careful about typos – they will take the site off-line until you remove them):

define(‘KEYY_DISABLE’, true);

(Put it near the top after the opening <?php line).

Best wishes,
David

P.S. I forgot to mention… I am told that we can also give you access to the 1.2.5 release via Apple’s “pre-release testing” channel. Please let us know if you are interested in that, and I will then ask our iOS lead to give you access.

Held up in review because Apple’s reviewer wrongly decided that the app can’t be used without signing up for an account on our website…. a conclusion that’s really bizarre, because no sign-up form even exists on the website. So, we’ve replied to that and are waiting for a fresh review.