#1784 - Tapatalk
-
By Lhasadreams
- Added
- 2 views
| Identifier | #1784 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Tapatalk |
| Status | Completed |
| Handling member | Chris Graham |
| Addon | General / Uncategorised |
| Description | Fully implement a native Composr forum integration to Tapatalk.
What would be the cost? Very happy to sponsor this. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
Can I have a progress update for this please.
Cheers
Ade
I have completed working on methods and uploaded the code to our testing server, so that i can test tapatalk interaction with our plugin. I have registered our plugin to tapatalk, now i have to publish it, in order to test and fix the bugs.
Thanks & Regards,
Amit.
All the tapatalk methods have been implemented, i am trying to test this with taptalk live forum to do some final adjustments. I am working with their forum moderator to fix some issues. I shall update you shortly. Thanks
Excellent news :-)
How is the testing going ?
Cheers
Ade
While development, we came to know that their api documentation is quite buggy and leads to confusion. Tapatalk app is also not able to tell us how it fails. To overcome this, we have developed techniques to debug the incoming and outgoing requests for better trace through the functionality.
Now i have better visibility what is happening inside. I ll update you the status of testing on Thursday.
Thanks for bearing with me and your cooperation.
I've been working on this solidly since my last update. Unfortunately we have found large numbers of bugs/inconsistencies between the TapaTalk Android/iOS/Windows-Phone clients, and lots more errors in the documentation. I also unfortunately had missed implementing a part of the API which I am finishing now. We are conducting careful testing on a spreadsheet, ensuring all functionality is working for each individual part of the API.
Thank you so much for your continued effort on this - it is appreciated a lot.
Cheers
Ade
We had this "implemented" and mostly tested a few months back.
Then...
I took this over for "final" testing, but when verifying it in my exhaustive way I ended up finding a further (approx) 150 issues in Tapatalk's documentation, including lots of missing parts for newer stuff they since had in their client. Additionally a lot of conditions needed care, such as validation, performance considerations, making a more manageable API than the sample implementation had, proper unit testing, and so on. In short: huge amounts of extra work was actually required.
Finally we now have everything implemented including the non-documented parts of Tapatalk, everything passing our Code Quality Checker, all Tapatalk endpoints tested to work via unit tests, and push is implemented.
The extra work has been one of the road-blocks in getting v10 finished recently, as Tapatalk support is slated to come in with that (it's a very clean implementation, so some internal improvements have been made to Composr/Composr, rather than us hacking around any internal limitations). Generally also we have to catch up with the back-log of sponsored work like this, before continuing on with other v10 finalisations.
Now finally we are moving on to the Tapatalk client testing.