JJTech0130 / pypush

[being rewritten] Cross-platform iMessage POC
https://discord.gg/BVvNukmfTC
Other
3.56k stars 396 forks source link

Validation data expired #80

Closed selenium-can closed 9 months ago

selenium-can commented 10 months ago

I tried to update data.plist, but I got a raise Exception("Validation data expired! ") Could you please help me solve this headache? Also, how do I create a batch data.plist, or make it update automatically

selenium-can commented 10 months ago

I tried to update data.plist, but I got a raise Exception("Validation data expired! ") Could you please help me solve this headache? Also, how do I create a batch data.plist, or make it update automatically

on real mac or hackintosh you own, use this to get your data.plist extracted: https://github.com/JJTech0130/nacserver but for now its down as service, maybe next update will fix the current issue, join the discord server for more update and details

As for "on real mac or hackintosh you own, use this to get your data.plist extracted", I have tried and the error is "Response code: 6004 ", "Validation data expired! Now I don't know how to solve this problem, can you give me another contact information for you? It is convenient for me to communicate with you and thank you.

Kasherpete commented 9 months ago

Pypush is currently down, we're working hard to fix it atm.

elminson commented 9 months ago

Thank you @Kasherpete , I been running some test on my end. Looks like an issue with the self.queue in apns.py Let me know if you need any help

AngeloD2022 commented 9 months ago

Pypush is currently down, we're working hard to fix it atm.

Do we know which specific part(s) have been broken by Apple?

SpaceSaver commented 9 months ago

Pypush is currently down, we're working hard to fix it atm.

Do we know which specific part(s) have been broken by Apple?

Yes, will be published after Beeper Mini is fixed.

v-mod commented 9 months ago

So when can we expect that to be as i'm pretty sure beeper mini has resumed services if i'm not mistaken.

Cypheriel commented 9 months ago

Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know.

elminson commented 9 months ago

I can confirm the branch async branch works :), I will do some adjustment for my code :) @Cypheriel thank you so much

danipoak commented 9 months ago

Closing. Fixed with Async updates.

selenium-can commented 9 months ago

This problem is still unable to send messages, but can be logged in.

At 2023-12-12 06:19:18, "Mikel" @.***> wrote:

Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

SpaceSaver commented 9 months ago

This problem is still unable to send messages, but can be logged in. At 2023-12-12 06:19:18, "Mikel" @.> wrote: Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Are you on the async branch?

selenium-can commented 9 months ago

Yes, I am on async branch and couldn't send messages during today's test and did not enable hread.Message ID

At 2023-12-16 22:36:09, "SpaceSaver" @.***> wrote:

This problem is still unable to send messages, but can be logged in. At 2023-12-12 06:19:18, "Mikel" @.> wrote: Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Are you on the async branch?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

SpaceSaver commented 9 months ago

Yes, I am on async branch and couldn't send messages during today's test and did not enable hread.Message ID At 2023-12-16 22:36:09, "SpaceSaver" @.> wrote: This problem is still unable to send messages, but can be logged in. At 2023-12-12 06:19:18, "Mikel" @.> wrote: Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Are you on the async branch? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Apple appears to have blocked us again.

selenium-can commented 9 months ago

Oh my God, how can I solve this problem, can you help me solve, how often Apple blocks us?

At 2023-12-16 22:44:10, "SpaceSaver" @.***> wrote:

Yes, I am on async branch and couldn't send messages during today's test and did not enable hread.Message ID At 2023-12-16 22:36:09, "SpaceSaver" @.> wrote: This problem is still unable to send messages, but can be logged in. At 2023-12-12 06:19:18, "Mikel" @.> wrote: Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Are you on the async branch? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Apple appears to have blocked us again.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

SpaceSaver commented 9 months ago

Oh my God, how can I solve this problem, can you help me solve, how often Apple blocks us? At 2023-12-16 22:44:10, "SpaceSaver" @.> wrote: Yes, I am on async branch and couldn't send messages during today's test and did not enable hread.Message ID At 2023-12-16 22:36:09, "SpaceSaver" @.> wrote: This problem is still unable to send messages, but can be logged in. At 2023-12-12 06:19:18, "Mikel" @.> wrote: Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Are you on the async branch? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Apple appears to have blocked us again. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Whenever they feel like it. Which is becoming weekly.

selenium-can commented 9 months ago

Ha ha, it seems that this is a sad story. How can I learn to solve this problem as easily as you do?

At 2023-12-16 22:50:02, "SpaceSaver" @.***> wrote:

Oh my God, how can I solve this problem, can you help me solve, how often Apple blocks us? At 2023-12-16 22:44:10, "SpaceSaver" @.> wrote: Yes, I am on async branch and couldn't send messages during today's test and did not enable hread.Message ID At 2023-12-16 22:36:09, "SpaceSaver" @.> wrote: This problem is still unable to send messages, but can be logged in. At 2023-12-12 06:19:18, "Mikel" @.> wrote: Hello. This issue should be fixed in the latest commit of the async branch. If this does not solve the issue, please let us know. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Are you on the async branch? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.> Apple appears to have blocked us again. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

Whenever they feel like it. Which is becoming weekly.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

SpaceSaver commented 9 months ago

What do you plan on using the project for?

selenium-can commented 9 months ago

I plan to send regular greetings to my friends and regular tasks to myself. And chatgpt can help me reply automatically when my friends reply to my messages. For me, this is a challenging and meaningful thing.

At 2023-12-16 23:09:55, "SpaceSaver" @.***> wrote:

What do you plan on using the project for?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>