android-play-safetynet
android-play-safetynet copied to clipboard
Resolve Issue #19
getApkDigestSha256()
now null checks the backing field, and if is null, returns an empty byte array
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!
) and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
ℹ️ Googlers: Go here for more info.
I am an authorized contributor via my company’s CLA – Prosper Marketplace, Inc.
-Don Phillips
From: googlebot [email protected] Sent: Thursday, March 21, 2019 1:58 PM To: googlesamples/android-play-safetynet [email protected] Cc: Don Phillips [email protected]; Author [email protected] Subject: Re: [googlesamples/android-play-safetynet] Resolve Issue #19 (#20)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2F&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907439584&sdata=vacQ3WE%2FblMu7VFnDBXA58GYG7i0y0%2FRR4qzpuourZ0%3D&reserved=0 to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA datahttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2Fclas&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907439584&sdata=wE1EmC7kBImql3MpLIB3or9b5JfX%2F0QnNBoKsJcO%2FlE%3D&reserved=0 and verify that your email is set on your git commitshttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Farticles%2Fsetting-your-email-in-git%2F&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907449598&sdata=aYkp%2FAucTr%2FceNbYLDTO9gMCnp3Afb%2FkoMy1gmuOyaw%3D&reserved=0.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoothttp://go/cla#troubleshoot (Public versionhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopensource.google.com%2Fdocs%2Fcla%2F%23troubleshoot&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907459603&sdata=1SMfN%2BRVt%2FopVE7TS1Ed5ZqPFABZCzcpYbXHQnLFwwA%3D&reserved=0).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA datahttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2Fclas&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907459603&sdata=rmLg%2F4ipjt9xp8jG11iLYQFexIPuP8Rw9tWBElFO7FA%3D&reserved=0 and verify that your email is set on your git commitshttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Farticles%2Fsetting-your-email-in-git%2F&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907469608&sdata=1NMi9KQ5p%2Bb29oWdze2V6Dfw1uKKfYCXPZT472UYjuI%3D&reserved=0.
- The email used to register you as an authorized contributor must also be attached to your GitHub accounthttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsettings%2Femails&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907469608&sdata=UyaFHEd42LHFguNkorFW%2FxWBBCv7o4dZRxXSEhWC5a0%3D&reserved=0.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgooglesamples%2Fandroid-play-safetynet%2Fpull%2F20%23issuecomment-475399688&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907489622&sdata=lhcFXN6%2FV0ibksnQUhIU5DPqsbzW4MrLIn%2FcsEiDa40%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANHoPLgqW0--9s2xPE3zUeF4n9iZ9iChks5vY_JfgaJpZM4cCW8S&data=02%7C01%7Cdphillips%40prosper.com%7C54afeaf2a6e14796f63e08d6ae3fec18%7C924fb1d22d664b62aeca6517836f3b2f%7C1%7C0%7C636887986907489622&sdata=UyY7TBpExb4WGAZpG7Xph4XNC1HribBsct8wcp0XVTs%3D&reserved=0.
CONFIDENTIALITY STATEMENT: This email message, together with all attachments, is intended only for the individual or entity to which it is addressed and may contain legally privileged or confidential information. Any dissemination, distribution or copying of this communication by persons or entities other than the intended recipient, is strictly prohibited, and may be unlawful. If you have received this communication in error please contact the sender immediately and delete the transmitted material and all copies from your system, or if received in hard copy format, return the material to us via the United States Postal Service. Thank you.
Bump - is anyone from Google here?
Bump - it's been a month now, is anyone there?
I'm not from google - just found this from a random google search. But I think you might need to write I signed it!
in a reply to trigger the bot
@eedrah - worth a shot I guess. If those specific words are what's required, that bot's original message is poor.
@googlebot I signed it!
Is anyone responsible for this repository at this point?
@jfschmakeit ?