Archived

This topic is now archived and is closed to further replies.

mutilator

android resolved swiftkey

12 posts in this topic

seem to be getting a problem on the latest android mx5 release where swiftkey freezes when using maxthon. It only happens in maxthon normally on first use and doesn't happen in chrome. I'm using a samsung galaxy s7 edge (6.01) anyone else noticed this issue? (does not seem to happen on the default keyboard either or the previous beta)

Share this post


Link to post
Share on other sites

Same issue here, had to switch to default kb though still occasionally see freezing when typing in an address. Was waiting for 7000 to see if issue fixed.

Share this post


Link to post
Share on other sites

Thank you both for posting.

And thanks for the detailed information provided. I'll forward this issue to our Android team members.

Hope you two a nice day :1f60a:

 

BTW, which Maxthon android version are you using now, version 7000?  @mutilator @-=SD=-

Share this post


Link to post
Share on other sites

I'm using version 5.1.6000 and if your team are going to test it I'm using swiftkey version 6.4.4.78.

If 7000 is out for beta share the love by giving me access :p

Share this post


Link to post
Share on other sites

6000 here, same s7 edge and android version. Default kb still freezing on first address typing. Thought it was just swiftkey but its both. 

Share this post


Link to post
Share on other sites

Thank you both for replying. Our tester has tried on our testing device but cannot reproduce the problem. 

So could you please record a short video of the whole process and the freeze, so that our staff can have a look into it, if it's no bother. :1f60a:

BTW, the attached is our version 5.1.7000. You are welcome to download and have a try to see if the problem still exists.

Have a nice day, both friends.

mx_five_pre_mx5_e48c673_3007_5.1.7000_proguard.apk

Share this post


Link to post
Share on other sites

ok running the 5.1.7000 and it still does the same thing. ill try and film it when i get chance. The previous release to 6000 worked fine other than occasionally it crashed but that seems to be fixed now. So definitely heading in the right direction.

1 person likes this

Share this post


Link to post
Share on other sites
On 10/21/2016 at 5:24 PM, mutilator said:

Here you go, sorry for the amateurish video. Hope it helps

2016_10_21_09_46_52.mp4

Hi mutilator, thanks for the video. I've forward it to our testers to check, will get back to you soon.:1f60a:

Share this post


Link to post
Share on other sites
45 minutes ago, BugSir006 said:

Hi mutilator, thanks for the video. I've forward it to our testers to check, will get back to you soon.:1f60a:

If they want to test future beta's or see if a small fix works rather than a big release i don't mind being the guinea pig if they cant reproduce the problem. Also I'm on here daily so if Swiftkey release an update that fixes it etc. I'll leave a message here.

Share this post


Link to post
Share on other sites

Hello, bit of good news it looks like this issue has been fixed in MX 5.0.1 official (android) as i have been unable to replicate the bug. Thanks for all the help and getting this annoying issue fixed. Look forward to having a non crashing, reliable web browser with maxthon.

2 people like this

Share this post


Link to post
Share on other sites
On 10/27/2016 at 5:41 PM, mutilator said:

Hello, bit of good news it looks like this issue has been fixed in MX 5.0.1 official (android) as i have been unable to replicate the bug. Thanks for all the help and getting this annoying issue fixed. Look forward to having a non crashing, reliable web browser with maxthon.

Hi mutilator, thanks for trying the official version. 

 

How about @-=SD=- ? Have you tried in the new official version? Can you still reproduce the bug?

Share this post


Link to post
Share on other sites