The attached zip file includes a modified main.m file which implements the continueUserActivity method. Put it inside Files\Special.
Thanks Erel
Just added this piece. Still doesn't work but I guess it is because of server issues (*)
Considering that iOS doesn't even acknowledge your universal links I would say the issue is before B4i even comes into the picture.
Good catch, thanks. I had an extra character in the #Entitlement. Now iOS diagnosis utility recognizes the universal link. I have found out that for this iOS tool, only what the app declares is taken into account (doesn't even look at the webserver's AASA file)
(*) There is another problem that the server's AASA file is not valid because of a server certificate issue (AASA validity can be checked using this or other tools:
https://apnspush.com/aasa-validator/) -> also, seems that it is not enough to place the AASA file where it corresponds, since Safari navigator won't directly search for it in order to validate the universal link, but instead consult Apple's CDN -> this means that this apple service must be able to search/find the AASA file, meaning that the AASA CDN bot must not be blocked, among others.
(Follow-up, in case anyone might be after the same issue)
While the server certificate issue is solved, I found this:
https://nishbhasin.medium.com/apple-universal-link-setup-in-ios-131a508b45d1
There seems to be a way to check if universal links are well implemented in the app during development, apparently directly accessing the AASA file (which allows for on-the-fly changes during development, avoiding CDN propagation delay issues). It requires:
- Enabling develpment mode in the iPhone
- Using a development certificate/profile
- Add "?mode=developer" to the #Entitlement's domain
Unfortunately, it still doesn't work for me, perhaps because of the same certificate issues, so I'll have to wait until the customer fixes it
and see if more steps are needed.