How to change Dependencies download destination path?

Open
#1,356 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, csharp, unity
Domain
build-system, mobile-dev

Research direction

The issue names no file or test. Start by tracing how Firebase Messaging dependencies are downloaded into Assets/Plugins/Android in a Unity 2022.3 project, then compare that behavior with the requested Assets/ThirdParty/Firebase or Assets/Plugins/Firebase destinations. Done means the supported way to configure the destination is established, or the request is specified for implementation.

Written by the indexing model from the issue text.

Description

new
[READ] For Firebase Unity SDK issues, please report to Firebase Unity open-source

Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.

[REQUIRED] Please fill in the following fields:
  • Unity editor version: 2022.3
  • Firebase Unity SDK version: 11.5.0.
  • Source you installed the SDK: unitypackage (.unitypackage or Unity Package Manager)
  • Problematic Firebase Component: Messaging___ (Auth, Database, etc.)
  • Other Firebase Components in use: _no other (Auth, Database, etc.)
  • Additional SDKs you are using: my own custom activity (Facebook, AdMob, etc.)
  • Platform you are using the Unity editor on: Windows (Mac, Windows, or Linux)
  • Platform you are targeting: Android (iOS, Android, and/or desktop)
  • Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)
[REQUIRED] How to change Dependencies download destination path?

currently It will download into Assets/Plugins/Android folder?,
But I wan't things to be more organized ,for example ,Idealy,I want everything releated to firebase reside in Assets/ThirdParty/Firebase
Or Assets/Plugins/Firebase

Dominant language
C#
Stars
923
Forks
456
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/quickstart-unity

All issues in firebase/quickstart-unity

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.