Skip to content

Fatal error: could not load resource bundle when using packages with resources #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
alfavata opened this issue Feb 3, 2021 · 1 comment
Closed

Fatal error: could not load resource bundle when using packages with resources #5

alfavata opened this issue Feb 3, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@alfavata
Copy link

alfavata commented Feb 3, 2021

I'm trying to integrate PhoneNumberKit in my lambda, and according to this PR it should work on Linux servers.

However, when I build and deploy my lambda using swift-lambda it encounters the following error:

Fatal error: could not load resource bundle: from /var/task/PhoneNumberKit_PhoneNumberKit.resources or /Users/alfavata/Code/ios-hiya/CallLogLambda/.build/x86_64-unknown-linux/release/PhoneNumberKit_PhoneNumberKit.resources: file PhoneNumberKit/resource_bundle_accessor.swift, line 11

(Note that it's referring to the path on my local machine)

I've put a minimal example package here as suggested by @helje5
@helje5 helje5 added bug Something isn't working enhancement New feature or request labels Feb 3, 2021
helje5 added a commit that referenced this issue Feb 3, 2021
@helje5
Add support for SPM resources
dac42bc 
This should fix issue #5. If SPM produces
*.resources directories in the build dir,
we copy them over.
@helje5
Copy link
Member

helje5 commented Feb 3, 2021

Works now.

@helje5 helje5 closed this as completed Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alfavata @helje5