PerfectlySoft / PerfectlySoft/Perfect-Notifications
Why it reading AuthKey from build path. Could you please explain? How we can configure build path on production
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 117
- Forks
- 29
- Avg merge
- 16m
- Merged PRs (30d)
- 1
Description
Fatal error: The private key file "/AuthKey_A9HP4L5K6P.p8" does not exist. Current working directory: /Users/chandrakant/Library/Developer/Xcode/DerivedData/ashi-api-ackosslvopviteghopwhwturjxql/Build/Products/Debug/
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.
Research direction
The report provides no source file, test, or entry point to inspect. Begin by locating where AuthKey_A9HP4L5K6P.p8 is resolved and how the current working directory is used, then reproduce the production configuration path. Done means the library’s expected key location or configuration is documented and the fatal missing-file error is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100