Skip to main content

How to get mobilesdk_app_id parameter in google-services.json

The google-services.json file is generally placed in the app/ directory, but as of version 2.0.0-alpha3 of the plugin support was added for build types, which would make the following directory structure valid:
app/src/
    main/google-services.json
    dogfood/google-services.json
    mytype1/google-services.json

mobilesdk_app_id :
You can create a new project and add services to it. This website will automatically generate a google-services.json file for your new project.

Comments

Post a Comment

Popular posts from this blog

Access can be package - Private, Protected and Public ( Differences )

Java has four access modifier namely  private ,  protected  and  public . package level access is  default access  level provided by Java  if no access modifier is specified. These access modifiers are used to restrict accessibility of a class, method or variable on which it applies. We will start from private access modifier which is most restrictive access modifier and then go towards public which is least restrictive access modifier, along the way we will see some best practices while using access modifier in Java and some examples of using  private  and  protected  keywords. private keyword in Java private  keyword or modifier in java can be applied to member field, method or nested class in Java. you can not use the  private  modifier on top level class.  private  variables, methods, and class are only accessible on the class on which they are declar...
Post a Comment
Read more

org.gradle.api.internal.tasks.DefaultTaskInputs$TaskInputUnionFileCollection cannot be cast to org.gradle.api.internal.file.collections.

Error:Cause: org.gradle.api.internal.tasks.DefaultTaskInputs$TaskInputUnionFileCollection cannot be cast to org.gradle.api.internal.file.collections.DefaultConfigurableFileCollection Possible causes for this unexpected error include: Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.) Re-download dependencies and sync project (requires network) The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem. Stop Gradle build processes (requires restart) Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project. In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes. Solutions: Upgrade your gradle build tools to the latest version. One easy way to do this is to add the latest version of the build tools as a depend...
1 comment
Read more