Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error codes and path checks for use in automation #69

Open
aceslick911 opened this issue Jan 23, 2023 · 0 comments
Open

Error codes and path checks for use in automation #69

aceslick911 opened this issue Jan 23, 2023 · 0 comments

Comments

@aceslick911
Copy link

aceslick911 commented Jan 23, 2023

For yurl to be super useful as part of automation/testing I'd recommend throwing an error code in the CLI when the deeplinking is presumed to be not working due to a failure condition.

This would mean teams could potentially use yurl commands in CI or automation to detect when problems with deeplinking happen.

Specifics:

  • should not throw error code if CDN AASA is out of date - this would cause CI to not be very useful during PRs before 'releases'
  • we should add code to validate the AASA against spec provided by apple (applinks, details, paths, webcredentials)
  • we could add code to validate url PATHS against the AASA defined paths and/or appid

eg.

> yurl aasa validate "https://MYDOMAIN.com/PATH1/PATH2" "1234AAAA" "com.MYDOMAIN.MYAPP.APP"

< AASA Active validation [pass]
< AASA path: /PATH1/PATH2 [failed: no match for "com.MYDOMAIN.MYAPP.APP"]
< "/PATH1/PATH2" provided does not match any of:
< https://MYDOMAIN.com/PATH3
< https://MYDOMAIN.com/PATH4

exited with error code 1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant