[GH-ISSUE #209] How can I enable push notifications? #65

Closed
opened 2026-03-04 00:23:33 +03:00 by kerem · 4 comments
Owner

Originally created by @btglr on GitHub (Jun 2, 2022).
Original GitHub issue: https://github.com/SignTools/SignTools/issues/209

Hello!

Sorry to bother you again, now that I can get my apps properly signed I'm trying to get push notifications to work. I've generated a distribution certificate, signed my app with it and the app asks me if I want to enable notifications. I allowed them but I still don't get anything. I saw in this issue that you said both the development and distribution certificates/keys are needed, so I signed the app using those again - but I still don't get push notifications.

Is there anything else I'm supposed to do?

Thanks!

Originally created by @btglr on GitHub (Jun 2, 2022). Original GitHub issue: https://github.com/SignTools/SignTools/issues/209 Hello! Sorry to bother you again, now that I can get my apps properly signed I'm trying to get push notifications to work. I've generated a distribution certificate, signed my app with it and the app asks me if I want to enable notifications. I allowed them but I still don't get anything. I saw in [this issue](https://github.com/SignTools/SignTools/issues/96#issuecomment-903457794) that you said both the development and distribution certificates/keys are needed, so I signed the app using those again - but I still don't get push notifications. Is there anything else I'm supposed to do? Thanks!
kerem closed this issue 2026-03-04 00:23:34 +03:00
Author
Owner

@ViRb3 commented on GitHub (Jun 2, 2022):

You'll need a few things:

  1. A clean, unmodified IPA, with all entitlements intact. I recommend dumping and decrypting it yourself using a jailbroken device. You can inject any tweaks you want through the "Advanced" tab in SignTools.

  2. A p12 with both development and distribution certificate inside. To confirm if it worked, check for the following message in your builder logs:

    Using distribution certificate
    
  3. Tick "Force original bundle ID" from the "Advanced" tab in SignTools.

<!-- gh-comment-id:1145054790 --> @ViRb3 commented on GitHub (Jun 2, 2022): You'll need a few things: 1. A clean, unmodified IPA, with all entitlements intact. I recommend dumping and decrypting it yourself using a jailbroken device. You can inject any tweaks you want through the "Advanced" tab in SignTools. 2. A p12 with both development and distribution certificate inside. To confirm if it worked, check for the following message in your builder logs: ``` Using distribution certificate ``` 3. Tick "Force original bundle ID" from the "Advanced" tab in SignTools.
Author
Owner

@btglr commented on GitHub (Jun 2, 2022):

3. Tick "Force original bundle ID" from the "AdvanceD" tab in SignTools.

That did it. According to the tooltip it breaks all other entitlements but so far I haven't noticed anything breaking.

I'm wondering though, now that the bundle ID is identical to the original one why are self-signed apps not detected the same way the original apps are in autofill? For example with the original Twitter app my account is detected and shows up above the keyboard from my autofill service, whereas with the self-signed app it doesn't.

<!-- gh-comment-id:1145078083 --> @btglr commented on GitHub (Jun 2, 2022): > 3. Tick "Force original bundle ID" from the "AdvanceD" tab in SignTools. That did it. According to the tooltip it breaks all other entitlements but so far I haven't noticed anything breaking. I'm wondering though, now that the bundle ID is identical to the original one why are self-signed apps not detected the same way the original apps are in autofill? For example with the original Twitter app my account is detected and shows up above the keyboard from my autofill service, whereas with the self-signed app it doesn't.
Author
Owner

@ViRb3 commented on GitHub (Jun 2, 2022):

why are self-signed apps not detected the same way the original apps are in autofill

Most likely because the team id is different, and that is a part of the application id, which is what iOS uses most of the time to identify an app.

<!-- gh-comment-id:1145080581 --> @ViRb3 commented on GitHub (Jun 2, 2022): > why are self-signed apps not detected the same way the original apps are in autofill Most likely because the team id is different, and that is a part of the application id, which is what iOS uses most of the time to identify an app.
Author
Owner

@btglr commented on GitHub (Jun 2, 2022):

I see. Thanks for the help!

<!-- gh-comment-id:1145082308 --> @btglr commented on GitHub (Jun 2, 2022): I see. Thanks for the help!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/SignTools#65
No description provided.