Unexpected error occuring after the update

[martin@rootjazz]

Anyway.. so the problem is just twitter ask me to change password.. but if the account lang is not engliah TD won't detect it.. am I right?

I don't know. It should. I as just speculating that could be why it didn't. Or maybe twitter changed the pattern so program didn't detect it as I haven't seen it yet.

But is that tge only problem? because while no actions work when I'm sure some accounts work without any problem.. thia means there is another problem different than just require to change password.

As twitter is always changing, things that worked, will stop working, as they add new checks that I haven't seen yet, things will fail as every little thing twitter does needs custom code. So it is a custom battle of updates trying to handle the new things and trying to handle things nicely that haven't even happened yet

[martin@rootjazz]

I counter this problem today.

Code: Select all

Validate account failed: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.:

I can't tweet nither follow or verify account..etc

Log_id: logs_61648

Not finding any issues in logs. I know it is not always possible, but it really does help if can generate issue specific logs as explained here:

https://rootjazz.com/forum/viewtopic.php?f=23&t=1634

Same for providing the information as requested in the post as well.
What specific action.
How you create it.
Shared action / single account action
What logs you saw to notice the issue
Does it apply to all actions or some actions.
Does it apply to all accounts / some accounts

etc etc


Regards,
Martin

[martin@rootjazz]

ok found the issue in account verify actions. Twitter is returning the force relogin / verify response to JSON requests which is new. Will sort something to handle that

[martin@rootjazz]

also seems to be a language issue as well. Some english text was checked for. Unfortunately it seems that twitter does not provide non-language specific IDs to detect this

[Fahad]

also seems to be a language issue as well. Some english text was checked for. Unfortunately it seems that twitter does not provide non-language specific IDs to detect this

I think that could be overcoming by provide an option in update accounts to change language.

Twitter is a headache

[Fahad]

I just test one account.. and there is a very very strange problem.

I try to update account.. it fails and give this logs:

Code: Select all

19:51:50: Current time: 19:51:00
19:51:50:  Account Can run: 19:51:00  start: 08:00:00 / stop: 20:00:00
19:51:53: Starting: 05/08/2019 19:51 PM
19:51:57: Checking account: @@
19:51:57: Login: @@ : @@ Proxy: My_Proxy
19:51:57: UA: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
19:51:57: Login: get: https://twitter.com/
19:51:57: GET: https://twitter.com/
19:51:58: GET: 200
https://twitter.com/
19:51:58: Login: Success validate:
19:52:16: * WARNING: 'We have detected unusual activity on your account. For your security, your account has been locked until you change your password.'
You *may* additionally be required to receive a SMS on the assigned phone number for the account: 
19:52:16: Already logged in: @@
19:52:16: Scraping Daily stats for: @@
19:52:16: Current time: 19:52:00
19:52:16:  Account Can run: 19:52:00  start: 08:00:00 / stop: 20:00:00
19:52:16: UserDetails: https://mobile.twitter.com/@@ with: @@  Proxy: My_Proxy
19:52:16: Scrape from users: 1
19:52:16: Scrape details from: 1 inputs
19:52:16: Getting user details for :1 ids
19:52:16: GET: https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
19:52:17: GET: 403
https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
19:52:17: FAILED GET: (120058) 403
https://api.twitter.com/1.1/users/lookup.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&skip_status=1&screen_name=@@
19:52:17: error: deserialising: VKoW7G3j0 type: List`1
19:52:17: {"errors":[{"code":326,"message":"To protect our users from spam and other malicious activity, this account is temporarily locked. Please log in to https://twitter.com to unlock your account.","sub_error_code":0,"bounce_location":"https://twitter.com/account/access"}]}
19:52:17: ERROR: scrape users from ID :Cannot deserialize the current JSON object (e.g. {"name":"value"}) into type 'System.Collections.Generic.List`1[LibTwitterJsonData.JsonUser]' because the type requires a JSON array (e.g. [1,2,3]) to deserialize correctly.
To fix this error either change the JSON to a JSON array (e.g. [1,2,3]) or change the deserialized type so that it is a normal .NET type (e.g. not a primitive type like integer, not a collection type like an array or List<T>) that can be deserialized from a JSON object. JsonObjectAttribute can also be added to the type to force it to deserialize from a JSON object.
Path 'errors', line 1, position 10.
19:52:17: No users found for: https://mobile.twitter.com/@@
19:52:17: * FAILED: UserDetails: https://mobile.twitter.com/@@ with: @@
19:52:17: 0
<null>
<null>
19:52:17: * ERROR: scraping stats: Object reference not set to an instance of an object.
19:52:17: Current time: 19:52:00
19:52:17:  Account Can run: 19:52:00  start: 08:00:00 / stop: 20:00:00
19:52:17: Update Details:  with: @@  Proxy: My_Proxy
19:52:17: WARNING nothing to update
19:52:17: Current time: 19:52:00
19:52:17:  Account Can run: 19:52:00  start: 08:00:00 / stop: 20:00:00
19:52:17: User Header: My_Path\1 (11).jpg with: @@  Proxy: My_Proxy
19:52:17: upload profile image: My_Path\1 (11).jpg to: @@
19:52:17: Upload: My_Path\1 (11).jpg
19:52:17: buffer: 60909
19:52:17: POST: https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=60909&media_type=image%2Fjpg&media_category=tweet_image
19:52:17: POST: 403
https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=60909&media_type=image%2Fjpg&media_category=tweet_image
19:52:17: FAILED POST: (256853) 403
https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=60909&media_type=image%2Fjpg&media_category=tweet_image
19:52:17: * UNKNOWN ERROR OCCURRED - see logs for more info.
If the problem continues, please submit logs to support.
Object reference not set to an instance of an object.

19:52:18: finished processThread: updateaccounts 80a08708-58c3-4775-a7b5-a66a11b0e09e
19:58:36: clone: updateaccounts 80a08708-58c3-4775-a7b5-a66a11b0e09e

After that I verify account and it verified without any problem..

I log in manually though TD and post a tweet.. everything is good! (without require any PV or captcha!)

I redo the same action to update account and here is the log:

Code: Select all

19:58:36: Current time: 19:58:00
19:58:36:  Account Can run: 19:58:00  start: 08:00:00 / stop: 20:00:00
19:58:36: Starting: 05/08/2019 19:58 PM
19:58:40: Checking account: @@
19:58:40: Current time: 19:58:00
19:58:40:  Account Can run: 19:58:00  start: 08:00:00 / stop: 20:00:00
19:58:40: Update Details:  with: @@  Proxy: My_Proxy
19:58:40: WARNING nothing to update
19:58:40: Current time: 19:58:00
19:58:40:  Account Can run: 19:58:00  start: 08:00:00 / stop: 20:00:00
19:58:40: User Header: My_Path\1 (11).jpg with: @@  Proxy: My_Proxy
19:58:40: upload profile image: My_Path\1 (11).jpg to: @@
19:58:40: Upload: My_Path\1 (11).jpg
19:58:40: buffer: 60909
19:58:40: POST: https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=60909&media_type=image%2Fjpg&media_category=tweet_image
19:58:40: POST: 202
https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=60909&media_type=image%2Fjpg&media_category=tweet_image
19:58:40: Uploading media buffer: 60909
19:58:40: Uploading chunk: 1 My_Path\1 (11).jpg
19:58:40: POST: https://upload.twitter.com/i/media/upload.json?command=APPEND&media_id=1158422132210249728&segment_index=0
19:58:41: POST: 204
https://upload.twitter.com/i/media/upload.json?command=APPEND&media_id=1158422132210249728&segment_index=0
19:58:41: Buffer uploaded: 60909/60909
19:58:41: POST: https://upload.twitter.com/i/media/upload.json?command=FINALIZE&media_id=1158422132210249728
19:58:42: POST: 201
https://upload.twitter.com/i/media/upload.json?command=FINALIZE&media_id=1158422132210249728
19:58:42: Finalizing: My_Path\1 (11).jpg
19:58:42: MediaID: 1158422132210249728
19:58:42: mediaId   : 1158422132210249728
19:58:42: POST: https://api.twitter.com/1.1/account/update_profile_image.json
19:58:43: POST: 200
https://api.twitter.com/1.1/account/update_profile_image.json
19:58:43: * SUCCESS: User Header: My_Path\1 (11).jpg with: @@
19:58:43: Current time: 19:58:00
19:58:43:  Account Can run: 19:58:00  start: 08:00:00 / stop: 20:00:00
19:58:43: User Header: My_Path\1 (3).jpg with: @@  Proxy: My_Proxy
19:58:43: upload header profile banner: My_Path\1 (3).jpg to: @@
19:58:43: Upload: My_Path\1 (3).jpg
19:58:43: buffer: 114794
19:58:43: POST: https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=114794&media_type=image%2Fjpg&media_category=tweet_image
19:58:43: POST: 202
https://upload.twitter.com/i/media/upload.json?command=INIT&total_bytes=114794&media_type=image%2Fjpg&media_category=tweet_image
19:58:43: Uploading media buffer: 114794
19:58:43: Uploading chunk: 1 My_Path\1 (3).jpg
19:58:43: POST: https://upload.twitter.com/i/media/upload.json?command=APPEND&media_id=1158422143996239873&segment_index=0
19:58:44: POST: 204
https://upload.twitter.com/i/media/upload.json?command=APPEND&media_id=1158422143996239873&segment_index=0
19:58:44: Buffer uploaded: 100000/114794
19:58:44: Uploading chunk: 2 My_Path\1 (3).jpg
19:58:44: POST: https://upload.twitter.com/i/media/upload.json?command=APPEND&media_id=1158422143996239873&segment_index=1
19:58:45: POST: 204
https://upload.twitter.com/i/media/upload.json?command=APPEND&media_id=1158422143996239873&segment_index=1
19:58:45: Buffer uploaded: 114794/114794
19:58:45: POST: https://upload.twitter.com/i/media/upload.json?command=FINALIZE&media_id=1158422143996239873
19:58:46: POST: 201
https://upload.twitter.com/i/media/upload.json?command=FINALIZE&media_id=1158422143996239873
19:58:46: Finalizing: My_Path\1 (3).jpg
19:58:46: MediaID: 1158422143996239873
19:58:46: mediaId: 1158422143996239873
19:58:46: POST: https://api.twitter.com/1.1/account/update_profile_banner.json
19:58:47: POST: 200
https://api.twitter.com/1.1/account/update_profile_banner.json
19:58:47: * SUCCESS: User Header: My_Path\1 (3).jpg with: @@
19:58:47: Set TrendCountry
19:58:47: Current time: 19:58:00
19:58:47:  Account Can run: 19:58:00  start: 08:00:00 / stop: 20:00:00
19:58:47: TrendCountry: WOEID:  with: @@  Proxy: My_Proxy
19:58:47: POST: https://api.twitter.com/1.1/account/settings.json
19:58:47: POST: 200
https://api.twitter.com/1.1/account/settings.json
19:58:47: * SUCCESS: TrendCountry: WOEID:  with: @@
19:58:47: Started: 05/08/2019 19:58 PM
Finished: 05/08/2019 19:58 PM
ID: 66d5bb5a-291a-4987-a8b1-e138446c4ba8
19:58:47: Action ran for: 0hr:0min:11s
19:58:47: finished processThread: updateaccounts 66d5bb5a-291a-4987-a8b1-e138446c4ba8

Could that give any help? I hope so..

Log_id: logs_37864

[martin@rootjazz]

ok, might be able to handle this. The next update will include this feature. I shall let you know when it is ready.



Regards,
Martin

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html

[Fahad]

Thanks..

Testing.. everything looks good.. I hope it worked flawless

[martin@rootjazz]

I hope it worked flawless

Of course!