kivy / kivy/python-for-android
Recipe: `aioquic`
- Dominant language
- Python
- Stars
- 8.9k
- Forks
- 2k
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 9
Description
发生异常: ImportError (note: full exception trace is shown but execution is paused at: )
dlopen failed: "/data/data/org.test.myapp/files/app/_python_bundle/site-packages/aioquic/_buffer.abi3.so" is for EM_X86_64 (62) instead of EM_AARCH64 (183)
requirements = python3,kivy,pyjnius,android,plyer,debugpy,aioquic,bcrypt,attr,attrs,certifi,cffi,cryptography,debugpy,idna,Jinja2,jnius,pyasn1,pyasn1_modules,pycparser,pyOpenSSL,requests,service-identity,six,urllib3,charset-normalizer==2.1.1
p4a.extra_pip_args = --no-binary=aioquic
# (str) Custom source folders for requirements
# Sets custom source for any requirements with recipes
# requirements.source.kivy = ../../kivy
from aioquic.asyncio import connect, QuicConnectionProtocol
from aioquic.quic.configuration import QuicConfiguration
from aioquic.quic.events import ProtocolNegotiated, ConnectionTerminated
how to sovle aioquic/_buffer.abi3.so" is for EM_X86_64 (62) instead of EM_AARCH64 (183)?
Contributor guide
Research direction
Start by reproducing the Android build with the listed requirements and p4a.extra_pip_args, then inspect the generated aioquic/_buffer.abi3.so and its reported architecture. Compare the package output with the target EM_AARCH64 device. Done means the APK builds and imports aioquic without the EM_X86_64 versus EM_AARCH64 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, python
- Domain
- build-system, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100