search

ProgressNS / sidekick-feedback

This repository is for feedback regarding NativeScript Sidekick. Use the issues system here to submit feature requests or vote for existing ones.
45 stars 9 forks source link

Cloud build SHA certificate fingerprint (debug) #270

Open keerl opened 6 years ago

keerl commented 6 years ago

Please, provide the details below:

Did you verify whether this issue has already been reported here?

Yes

Tell us about the problem

I am building an application that uses Firebase Authentication and it requires me to add the SHA1 certificate fingerprint to the Firebase console. The problem is when I do a cloud build (debug mode) it seems to use a different certificate every time so I can never add the correct signature to Firebase because it is constantly changing. If I do a local build, everything works fine. Hopefully that makes sense, I'm just wondering if there is a solution/work-around to this problem.

Which platform(s) does the issue occur on?

Android
Windows

Provide the following version numbers that the issue occurs with:

How to obtain this information is explained in the Gather information about your development environment section.

Does this issue happen every time?

Yes

tsvetie commented 6 years ago

Hi @keerl, I apologize for the late reply. Your case sparked a couple of discussions as it is valid and right now, we do not have a very good solution. The idea that we came up with, is to allow the user to specify a certificate for Android Debug builds (currently, you can do this for Android Release builds only). I logged a feature request in NS CLI - as we need the support there first, and then we will update Sidekick to support this as well.

I do not have a very good workaround for the time being, but in case you need one, I can tell you how to modify the code in order to be able to run cloud debug builds with a specific certificate with NS CLI. Your other option is to use local builds as you already checked that these work for you.

On a side note, can you give me a bit more information about your development process? In particular, I am curious how you get the fingerprint when using local builds.

keerl commented 6 years ago

Hi @tsvetie Thanks for your response. If I am understanding you correctly you're saying there is a way to modify the code to be able to run cloud debug builds with a specific certificate currently? Does that solution work inside of Sidekick still?

This may be a noob question, but what is the difference between Debug and Release mode? Is there any downside of developing in Release mode? If there's not, I could just put the certificate I want to use there.

Also, the way I get the fingerprint from local builds is by following these instructions.

keerl commented 6 years ago

Upon testing I see that LiveSync does not work on release mode, so I see the need for Debug mode now.

tsvetie commented 6 years ago

Hey @keerl,

Yes, if you develop with Release builds, you will not be able to Debug or enable LiveSync.

Regarding the code change I mentioned - my idea was to modify the code of NS CLI and its cloud extension and to use NS CLI commands. In this case, Sidekick will still not support a specified certificate for Debug builds. However, upon further discussions, we realized that changing the code will still not make the cloud build use the specified certificate. So, unfortunately, I mislead you by saying that - there is no workaround. You are currently stuck with local builds. I will try to move this feature up the priority list because of that, but you can get that feature no sooner than NS CLI 5.0.

keerl commented 6 years ago

Well thanks for looking into it, I really appreciate it! It is not a critical feature for me right now, I can work around it until this feature comes out in a version >= 5.0.

imperatormk commented 5 years ago

Any news on this?