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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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