Android Question B4A Screenshot not working

johndb

Active Member
Licensed User
Longtime User
I encounter the following error when I attempt a screenshot using the current B4A 6.5 version. What would cause this and has anyone encountered this before. The android version is 7.1.1.

[SOLVED] Problem solved .... It appears that you cannot store the Android SDK on Dropbox for the proper operation of the B4A IDE screenshot tool. I changed the Configuration path to the SDK located on the local drive and it now works properly.

Screenshot error.PNG
 
Last edited:

johndb

Active Member
Licensed User
Longtime User
Did it previously work?

The screenshot feature wasn't changed in v6.50.
Yes it did but hadn't used the tool since late last year. I'm now preparing my "Play" screen images and encountered the error.
 
Upvote 0

johndb

Active Member
Licensed User
Longtime User
I tried it using my laptop and received the same error that I encountered on my PC. I think the problem may be caused by the way I have my B4A development files configured as I use Dropbox for all my libraries, projects, SDK, and Java components. Normally, this works very well where I can works on B4X projects either from my office PC or on the road with my laptop but may be causing a bit of confusion with the B4X IDE. I'll reconfigure it as see if a get the same errors.
 
Upvote 0

johndb

Active Member
Licensed User
Longtime User
I tried it using my laptop and received the same error that I encountered on my PC. I think the problem may be caused by the way I have my B4A development files configured as I use Dropbox for all my libraries, projects, SDK, and Java components. Normally, this works very well where I can works on B4X projects either from my office PC or on the road with my laptop but may be causing a bit of confusion with the B4X IDE. I'll reconfigure it as see if a get the same errors.
Problem solved .... It appears that you cannot store the Android SDK on Dropbox for the proper operation of the B4A IDE screenshot tool. I changed the Configuration path to the SDK located on the local drive and it now works properly.
 
Upvote 0
Top