We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Hi there
I'm using HaishinKit.swift package in my React Native third-party library here
My HaishinKit pod version was 1.2.7 and I wanted to update it to 1.4.1 but when I compile example project it gives these errors
I'm thinking it happens because Logger dependency. Do you have any thoughts about it? @shogo4405
s.dependency "HaishinKit", "~> 1.2.7" to s.dependency "HaishinKit", "~> 1.4.1"
s.dependency "HaishinKit", "~> 1.2.7"
s.dependency "HaishinKit", "~> 1.4.1"
Compiling without any error
Example project version: "react-native": "0.63.5"
No response
The text was updated successfully, but these errors were encountered:
Haishinkit.swift
1.3.0
I added the os.Logger.
I think it's a compiler problem of react-native. I have no idea.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Hi there
I'm using HaishinKit.swift package in my React Native third-party library here
My HaishinKit pod version was 1.2.7 and I wanted to update it to 1.4.1 but when I compile example project it gives these errors
![Screenshot 2023-01-07 at 01 36 34](https://user-images.githubusercontent.com/42299721/211111801-4b7291bb-d0ae-493f-809f-5e4206149e65.png)
I'm thinking it happens because Logger dependency.
Do you have any thoughts about it? @shogo4405
To Reproduce
s.dependency "HaishinKit", "~> 1.2.7"
tos.dependency "HaishinKit", "~> 1.4.1"
Expected behavior
Compiling without any error
Version
Example project version:
"react-native": "0.63.5"
Smartphone info.
No response
Additional context
No response
Screenshots
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: