Default browser request

Hi! Our app (blink.sh) has a browser integration focused on developers, and since latest changes now requires this entitlement to work properly.

I have been trying to reach out over email (default-browser-requests at apple.com) more than five times since before Christmas with no response - not even a "case received" or "confirmation from Apple" which is very strange.

I also reached out to "normal" developer relations through email and phone, and they took a deeper look at it. They told me that from information they got in this forum, the request may just take an "undetermined" amount of time, and that they could confirm we are using the right email.

Unfortunately we have had to launch the new version of our application and limit some of the functionality, which is causing a stir of support issues from our side.

Can anyone share what the process has been for them, and if they have received any confirmations along the way? Is there anyone here who could help us get in touch with the right person?

Thanks!

  • I’m a blink.sh user and would really appreciate this feature. Such a shame that Apple is not getting back to the developers and not allowing them to release a feature in demand.

  • I double the question because the required browser entitlement is really limiting the developers‘ productivity and it’s demotivating that the Apple support is acting so passively. There is nothing we can do except busy waiting :( I really hope this case can be resolved soon.

  • As a user and hobbyist developer, I'm hinging a device purchase based on whether or not this gets approved. The browser entitlement will enable blink to function perfectly for the entire web development loop.

Accepted Reply

We are happy to report that this was solved today. I'm adding some numbers here in case other people is in our situation, so you know what to expect (not trying to criticize in any way, some processes are what they are, we all try to do our best). In order for others to have a reference, the whole process has taken around 7 months. We were requested a couple changes in the last 2 - 3 months. Changes were about making sure the http/https routes were handled properly, so be ready for that. It would take around one month after implementing the fixes to get them approved or rejected, and there was no messaging or acknowledgement until that moment. So even if you don't receive any communication, just know that things may still be moving internally.

Hope this is helpful for everyone on what the process looks like.

Replies

I upvote this.

Apple needs to be more responsive to the very developers that have made the whole Apple iOS App Store such a success.

  • Just another Blink Shell user who would very much appreciate a response to this thread from Apple.

Add a Comment

Did you receive any update on this request? It's been ages since you submitted it. Apple is moving unacceptably slow on this.

Post not yet marked as solved Up vote reply of 1nu Down vote reply of 1nu

We are happy to report that this was solved today. I'm adding some numbers here in case other people is in our situation, so you know what to expect (not trying to criticize in any way, some processes are what they are, we all try to do our best). In order for others to have a reference, the whole process has taken around 7 months. We were requested a couple changes in the last 2 - 3 months. Changes were about making sure the http/https routes were handled properly, so be ready for that. It would take around one month after implementing the fixes to get them approved or rejected, and there was no messaging or acknowledgement until that moment. So even if you don't receive any communication, just know that things may still be moving internally.

Hope this is helpful for everyone on what the process looks like.