The BuildProcessorData.json and CustomAssetPacksData.json not generated
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp, unity
- Domain
- build-system, mobile-dev
Research direction
Reproduce Build > New Build > Play Asset Delivery, then inspect the PlayAssetDelivery/Build folder for BuildProcessorData.json, CustomAssetPacksData.json, and the *.bundle files. Compare the generated contents with the project description and determine whether the files are missing or being deleted unexpectedly; done means the expected build artifacts are present in the documented location.
Written by the indexing model from the issue text.
Description
I ran Build > New Build > Play Asset Delivery
Looked into the PlayAssetDelivery folder -> Build and those files are not there. Moreover, the files which were there got deleted.
Is that correct? It doesn't seem to match what was in the description for this project.
Moreover, aren't the *.bundle files also be placed under the PlayAssetDelivery -> Build folder? I don't see them placed there too.
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 303
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Unity-Technologies/Addressables-Sample
-
Difficulty 4/5 3-5 days Newbie friendliness 32/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Unity-Technologies/Addressables-Sample#98 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Unity-Technologies/Addressables-Sample#94 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
Unity-Technologies/Addressables-Sample#90 · 1 comment ·
All issues in Unity-Technologies/Addressables-Sample
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 75/100
sillsdev/languageforge-lexbox#2665 ·
-
bug documentation frontend
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
azurenoops/spin_agent#975 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SubtitleEdit/subtitleedit#15108 · 1 comment ·