Recent searches
No recent searches
![Greg Katechis's Avatar](https://support.zendesk.com/system/photos/1260910781490/T024F4EL1-U1D93RMBQ-298f26b1a7c7-512__1_.jpeg)
Greg Katechis
Joined Apr 14, 2021
·
Last activity Feb 13, 2025
Following
0
Followers
8
Total activity
1835
Votes
76
Subscriptions
733
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Greg Katechis
Greg Katechis commented,
Thanks for the update, glad it's working now!
View comment · Posted Feb 13, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hey Ron, sorry about that, looks like they gave you the wrong link. To get the URL of a recording, you actually need to use the List Comments endpoint (and the corresponding ticket ID of the call) and retrieve the URL from the `recording_url` property that will be returned.
View comment · Posted Feb 11, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hi Daniel,
You are correct that in this situation, you would need to permanently delete the entire ticket. The API is definitely an option, there are also third-party apps that can help if you prefer that method. Take a look at this article for more info and let us know if you have any other questions.
View comment · Posted Feb 11, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hi Anthony, sorry for the delay here…could you let me know if regenerating the secret and using that instead of the old one has presented the same problem for you?
View comment · Posted Feb 11, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hi David!
It sounds like there may be a piece missing in the payload, with the usual culprit being a missing `email_verified` parameter. Take a look at this documentation to see all the steps and if you are doing everything there and still seeing this issue, let me know and I'll open a private ticket so that we can investigate this further.
View comment · Posted Feb 11, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hi Neil!
I'll review this with our SDK team to get the wording correct and we'll make any necessary changes after that. Thanks for flagging this!
View comment · Posted Feb 11, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hi Zac!
I reached out to the team that handles this and it looks like this isn't something that we need to handle on our side. We utilize an AWS service for APNs, which means that we don't need to communicate directly with APNs. This means that everything should be just fine on the production switch date, but if you do encounter any issues, please let us know!
View comment · Posted Feb 11, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Back in November, Tipene had reached out to you privately to get some more details, but didn't get a response. If you can just follow the instructions in this article, we can see how we can best assist.
View comment · Posted Feb 10, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
Hi Dawid,
Could you provide some more information about the issue that you're having here? Please take a look at this article for the information that we need in order to assist with our SDKs.
View comment · Posted Feb 10, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments
Greg Katechis commented,
I'm not 100% clear at this point, but could you confirm that you do in fact have the full shared secret stored somewhere? If you test this on jwt.io, you will need to enter the shared secret in order to validate it and based on what you've said so far, I think that you may not have the full secret anywhere. If that's the case, I would recommend regenerating a new SDK and when you get the shared secret, you copy it down in a safe environment and then test it out. You will not be able to see the full shared secret once you are past this step.
View comment · Posted Jan 28, 2025 · Greg Katechis
0
Followers
0
Votes
0
Comments