Jump to content

SITE UPGRADE WARNING


S4GRU

Recommended Posts

I’m using Tapatalk Pro, latest update, and had no problems on iPhone 7 Plus on AT&T or WiFi. Also, Tapatalk Pro on Sprint iPad Air no problems.


Sent from my iPhone 7 Plus using Tapatalk Pro

Link to comment
Share on other sites

I'm using free Tapatalk (latest from Play Store) on Android 8.0 and another device on Android 7.0 and have never seen this issue. I also access from Chrome on Windows 7 from a different IP periodically (work PC), but mostly Tapatalk from at least 3 different IPs on two devices.

Link to comment
Share on other sites

54 minutes ago, DurhamHusker said:

I'm using free Tapatalk (latest from Play Store) on Android 8.0 and another device on Android 7.0 and have never seen this issue. I also access from Chrome on Windows 7 from a different IP periodically (work PC), but mostly Tapatalk from at least 3 different IPs on two devices.

i m having a problem altogether even if i m using a different ip address i still cant access it. and i dont use tapatalk half the time.....

Link to comment
Share on other sites

2 hours ago, bakedc4 said:

Android is 7.1.6(969) iPhone is 7.0.2

I did take advantage of the 99¢ sale years ago and got the pro version so it is ad free on all my deceives.

Sent from my 2PZC5 using Tapatalk
 

I have the "pro" or ad-free version as well, but still got blocked earlier this week. 

Link to comment
Share on other sites

17 minutes ago, danlodish345 said:

i m having a problem altogether even if i m using a different ip address i still cant access it. and i dont use tapatalk half the time.....

How are you verifying you are using a different IP address? Also, just having Tapatalk on your device can cause the issue (signed into S4GRU), you don't actually have to browse the forum continuously on Tapatalk to cause it.

Link to comment
Share on other sites

12 hours ago, Dkoellerwx said:

How are you verifying you are using a different IP address? Also, just having Tapatalk on your device can cause the issue (signed into S4GRU), you don't actually have to browse the forum continuously on Tapatalk to cause it.

Because I used my computer. And then I used my phone not hooked up to WiFi.

Link to comment
Share on other sites

I was using version 7.1.6 (build 969) on my Pixel; I logged out of my S4GRU account in Tapatalk so hopefully all of my IP blocks will eventually release. Tonight is the first time I've been able to access S4GRU from my home ISP IP in a couple of days.

-Mike

  • Like 1
Link to comment
Share on other sites

On 11/5/2017 at 1:48 AM, mikejeep said:

I was using version 7.1.6 (build 969) on my Pixel; I logged out of my S4GRU account in Tapatalk so hopefully all of my IP blocks will eventually release. Tonight is the first time I've been able to access S4GRU from my home ISP IP in a couple of days.

-Mike

I'm just using my browser until I'm sure Tapatalk has fixed their issues. 

Link to comment
Share on other sites

GOOD NEWS!  Or at least, I think it is.  I will remain *somewhat* skeptical until I see it fixes the problem.  I received a response from Tapatalk from my latest support ticket.  They say they found the problem of the error.  It's coded in their app.  It wasn't a problem in the past, but the newest version of IP Board has brought to light the loop in their coding that they didn't realize they created.

They say they are working to release a new version of the app that will fix the problem.  They provided no timeline, but said they would keep me updated about its release.

So, in the interim, you can either delete the Tapatalk app until they release a new version.  Or you can live with the CloudFront 48 hour blocks.  Personally, I uninstalled Tapatalk until its fixed.

Thanks for your patience.

Robert :welc2:

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

GOOD NEWS!  Or at least, I think it is.  I will remain *somewhat* skeptical until I see it fixes the problem.  I received a response from Tapatalk from my latest support ticket.  They say they found the problem of the error.  It's coded in their app.  It wasn't a problem in the past, but the newest version of IP Board has brought to light the loop in their coding that they didn't realize they created.
They say they are working to release a new version of the app that will fix the problem.  They provided no timeline, but said they would keep me updated about its release.
So, in the interim, you can either delete the Tapatalk app until they release a new version.  Or you can live with the CloudFront 48 hour blocks.  Personally, I uninstalled Tapatalk until its fixed.
Thanks for your patience.
Robert default_welc2.gif
Thanks for your work on this.

Any chance of a remedy for the other issue involving access to the S4GRU Club section?

Sent from my 2PZC5 using Tapatalk

Link to comment
Share on other sites

15 minutes ago, davidtm said:

Thanks for your work on this.

Any chance of a remedy for the other issue involving access to the S4GRU Club section?

Sent from my 2PZC5 using Tapatalk
 

They have not acknowledged that there is a problem.  Despite me providing evidence.  They say it is because of IP Board.  Which IP Board disputes.  With the old app, it went away one day with one of the updates.  Only to come back again.  Hopefully it will get resolved in the next Tapatalk app release.  But I wouldn't hold your breath.

Robert

  • Like 2
Link to comment
Share on other sites

They have not acknowledged that there is a problem.  Despite me providing evidence.  They say it is because of IP Board.  Which IP Board disputes.  With the old app, it went away one day with one of the updates.  Only to come back again.  Hopefully it will get resolved in the next Tapatalk app release.  But I wouldn't hold your breath.

Robert

S4gru with my wifi

 

 

Another Tapatalk forum with my wifi works....has to be ipboard or something else...cf239ee797cedbb40fc480e34dde659a.jpg3e103192509055ab9adb5a48aa4af56c.jpg

 

Sent from my Pixel 2 XL using Tapatalk

 

 

 

Link to comment
Share on other sites

1 hour ago, imex99 said:

S4gru with my wifi

 

 

Another Tapatalk forum with my wifi works....has to be ipboard or something else...cf239ee797cedbb40fc480e34dde659a.jpg3e103192509055ab9adb5a48aa4af56c.jpg

 

Sent from my Pixel 2 XL using Tapatalk

 

 

 

No, it's the app.  Just because it may not effect other platforms, doesn't mean the problem is IP Board.  Other sites might not cache on CloudFront/AWS.  So they don't get blocked for endless bootloops caused by Tapatalk coding errors.  Also, Tapatalk writes different codes for different hosting platforms.  Tapatalk even admitted yesterday they had a coding problem that they haven't addressed for years and just kept building on top of the problem update after update.  

Originally Tapatalk denied and denied the problem for weeks.  Thankfully IP Board and AWS kept digging more and more and providing more information to prove to Tapatalk they were the culprit.  If they had just said, whatever, there'd be no resolution.  I'm grateful that IP Board has such great support.  Because Tapatalk was not even being close to helpful to solve the problem.  They flat out ignored my first two support tickets.  It wasn't until some of you started marking their app rating down did I finally start getting somewhere with them.

  • Like 3
Link to comment
Share on other sites

No, it's the app.  Just because it may not effect other platforms, doesn't mean the problem is IP Board.  Other sites might not cache on CloudFront/AWS.  So they don't get blocked for endless bootloops caused by Tapatalk coding errors.  Also, Tapatalk writes different codes for different hosting platforms.  Tapatalk even admitted yesterday they had a coding problem that they haven't addressed for years and just kept building on top of the problem update after update.  
Originally Tapatalk denied and denied the problem for weeks.  Thankfully IP Board and AWS kept digging more and more and providing more information to prove to Tapatalk they were the culprit.  If they had just said, whatever, there'd be no resolution.  I'm grateful that IP Board has such great support.  Because Tapatalk was not even being close to helpful to solve the problem.  They flat out ignored my first two support tickets.  It wasn't until some of you started marking their app rating down did I finally start getting somewhere with them.
Ok, my app rating going down!

Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

I've been going back and forth with Tapatalk support, first they said an app update went out last week to resolve this, but I pointed out there have been no recent app updates. I just received a reply stating that the issue was actually resolved with a recent forum plugin update and they asked me to give @S4GRU a heads up. So Robert, see if there's something to update on your end I guess..

-Mike

Link to comment
Share on other sites

22 minutes ago, mikejeep said:

I've been going back and forth with Tapatalk support, first they said an app update went out last week to resolve this, but I pointed out there have been no recent app updates. I just received a reply stating that the issue was actually resolved with a recent forum plugin update and they asked me to give @S4GRU a heads up. So Robert, see if there's something to update on your end I guess..

-Mike

Thanks for the heads up.  I've updated the plugin to version 1.4.6 just now.  Let's see what happens!  :fingers:

  • Like 2
Link to comment
Share on other sites

7 minutes ago, mikejeep said:

An update for the Tapatalk Android app just dropped too. Perhaps these two updates will do the trick..

-Mike

I'm not seeing it, yet.  Says 10/19 update for me.  I'll keep looking for it.

Robert

Link to comment
Share on other sites

Weird. I luckily haven't had any problems since Tapatalk integration was added back. I wonder if it's something in our configuration or user accounts that's triggering it?

Sent from my Pixel 2 XL using Tapatalk

Link to comment
Share on other sites

I think disabling the "Show User Avatar" setting might be a workaround. IP Board reported that the loop occurs in the Avatar code. It may exist elsewhere too, but it's worth a try. I disabled it early this morning and so far no problems.

 

Sent from my Pixel XL using Tapatalk

 

 

 

 

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • So, in summary, here are the options I tested: T-Mobile intl roaming - LTE on SoftBank, routes back to the US (~220ms to 4.2.2.4) IIJ physical SIM - LTE on NTT, local routing Airalo - LTE on SoftBank and KDDI (seems to prefer SoftBank), routed through Singapore (SingTel) Ubigi - 5G on NTT, routed through Singapore (Transatel) US Mobile East Asia roaming - 5G on SoftBank, routed through Singapore (Club SIM) Saily - 5G on NTT, routed through Hong Kong (Truphone)...seems to be poorer routing my1010 - LTE on SoftBank and KDDI (seems to prefer KDDI), routed through Taiwan (Chunghwa Telecom) I wouldn't buy up on the T-Mobile international roaming, but it's a solid fallback. If you have the US Mobile roaming eSIM that's a great option. Otherwise Ubigi, Airalo, or my1010 are all solid options, so get whatever's cheapest. I wouldn't bother trying to find a physical SIM from IIJ...the Japanese IP is nice but there's enough WiFi that you can get a Japanese IP enough for whatever you need, and eSIM flexibility is great (IIJ as eSIM but seems a bit more involved to get it to work).
    • So, the rural part of the journey still has cell service for nearly all the way, usually on B18/19/8 (depending on whether we're talking about KDDI/NTT/SoftBank). I think I saw a bit of B28 and even n28 early on in the trip, though that faded out after a bit. Once we got to where we were going though, KDDI had enough B41 to pull 150+ Mbps, while NTT and SoftBank had B1/B3 IIRC. Cell service was likewise generally fine from Kawaguchiko Station to Tokyo on the express bus to Shinjuku Station, though there were some cases where only low-band LTE was available and capacity seemed to struggle. I also figured out what I was seeing with SoftBank on 40 MHz vs. 100 MHz n77: the 40 MHz blocks are actually inside the n78 band class, but SoftBank advertises them as n77, probably to facilitate NR CA. My phone likely preferred the 40 MHz slices as they're *much* lower-frequency, ~3.4 GHz rather than ~3.9, though of course I did see the 100 MHz slice being used rather often. By contrast, when I got NR on NTT it was either n28 10x10 or, more often, 100 MHz n78. As usual, EMEA bands on my S24 don't CA, so any data speeds I saw were the result of either one LTE carrier or one LTE carrier plus one NR carrier...except for B41 LTE. KDDI seems to have more B41 bandwidth live at this point, so my1010 or Airalo works well for this, and honestly while SoftBank and NTT 5G (in descending order of availability) have 5G that's readily available it may be diminishing returns, particularly given that I still don't know how to, as someone not from Hong Kong, get an eSIM that runs on SoftBank 5G that isn't the USM "comes for free with the unlimited premium package" roaming eSIM (NTT is easy enough thanks to Ubigi). In other news, I was able to borrow someone's Rakuten eSIM and...got LTE with it. 40 Mbps down, 20 Mbps up, 40ms latency to Tokyo while in Tokyo...which isn't any worse than the Japan-based physical SIMs I had used earlier. But not getting n77 or n257 was disappointing, though I had to test the eSIM from one spot rather than bouncing around the city to find somewhere with better reception. It's currently impossible to get a SIM as a foreigner that runs on Rakuten, so that was the best I could do. Also, I know my phone doesn't have all the LTE and 5G bands needed to take full advantage of Japanese networks. My S24 is missing: B21 (1500 MHz) - NTT B11 (1500 MHz) - KDDI, SoftBank B42 (3500 MHz) - NTT, KDDI, SoftBank n79 (4900 MHz) - NTT Of the above, B42/n79 are available on the latest iPhones, though you lose n257, and I'm guessing you're not going to find B11/B21 on a phone sold outside Japan.
    • T-Mobile acquiring SoniqWave's 2.5 GHz spectrum  Another spectrum speculator down! T-Mobile is acquiring all of their licenses and their leases. Details are lacking but it looks like T-Mobile might be giving them 3.45GHz in exchange in some of the markets where they're acquiring BRS/EBS to sweeten the deal and stay below the spectrum screen. Hopefully NextWave is at the negotiating table with T-Mobile so NYC can finally get access to the full BRS/EBS band as well. 
    • Maybe. The taller buildings on one side of the street all have Fios access and the NYCHA buildings are surrounded by Verizon macros that have mmWave. I don’t think this site will add much coverage. It’d be better off inside the complex itself.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...