Skip to content
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.

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

File missing building release APK #469

Closed
Zen-CODE opened this issue Feb 14, 2017 · 1 comment
Closed

File missing building release APK #469

Zen-CODE opened this issue Feb 14, 2017 · 1 comment

Comments

@Zen-CODE
Copy link
Member

Using the old_toolchain.
'''
Traceback (most recent call last):
File "/usr/local/bin/buildozer", line 9, in
load_entry_point('buildozer==0.33dev', 'console_scripts', 'buildozer')()
File "/media/richard/Acer/Richard/Repos/buildozer/buildozer/scripts/client.py", line 13, in main
Buildozer().run_command(sys.argv[1:])
File "/media/richard/Acer/Richard/Repos/buildozer/buildozer/init.py", line 1029, in run_command
self.target.run_commands(args)
File "/media/richard/Acer/Richard/Repos/buildozer/buildozer/target.py", line 91, in run_commands
func(args)
File "/media/richard/Acer/Richard/Repos/buildozer/buildozer/target.py", line 108, in cmd_release
self.buildozer.build()
File "/media/richard/Acer/Richard/Repos/buildozer/buildozer/init.py", line 211, in build
self.target.build_package()
File "/media/richard/Acer/Richard/Repos/buildozer/buildozer/targets/android.py", line 770, in build_package
copyfile(join(dist_dir, 'bin', apk), join(self.buildozer.bin_dir, apk))
File "/usr/lib/python2.7/shutil.py", line 82, in copyfile
with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory: u'/media/richard/Acer/CodeBox/Python/Kivy/SpeedTest/.buildozer/android/platform/python-for-android/dist/xxxx.com/bin/xxxx-release.apk'
'''

@kivybot
Copy link

kivybot commented May 16, 2017

Hey there!

We're automatically closing this issue since the original poster (or another commenter) hasn't yet responded to the question or request made to them 14 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.

Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

(Please note that this is an automated comment.)

@kivybot kivybot closed this as completed May 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants