(Pro) No module named 'fbs_runtime.application_context' when running app that was released via buildvm/runvm about fbs

[mherrmann]

I fixed these issues now in releases 1.2.0 and 1.2.1. If your purchase was within the last 12 months and you let me know the email you purchased with, then I'll give you access to the new version.

[mherrmann]

Yes, in that case you need to install Pro inside the Linux VM. So in your case, you need to somehow get fbs_pro.tar.gz into the Linux VM so it gets used by base.txt. You'd need to remove the fbs line there and only keep the .tar.gz line. fbs Pro should have a ready solution for this, at least in the manual. But I'm afraid I can't offer to add this for the Hobbyist license you purchased, which comes without support.

[apastel]

If this is the manual, there doesn't seem to be a documented solution for this: https://build-system.fman.io/manual/

Just wondering how other Pro users are doing this (without having to hack the Dockerfiles inside fbs_pro.tar.gz). How is it designed to work out of the box?

[meramsey]

put file in private url and then reference that in your requirements.txt

fbs @ https://somedomain/somesecretpath/fbs_pro-1.1.8.tar.gz

or you would need to volume mount the tarball inside and do a local install

[apastel]

Thanks @meramsey, both options work. I went with the latter by modifying the _defaults/src/build/docker/ubuntu/Dockerfile inside the fbs pro tarball to add this line:

COPY ./fbs_pro-1.1.3-apastel.tar.gz /root/${app_name}/

with that tarball residing locally in my requirements folder, and the requirements.txt file listing it as ./fbs_pro-1.1.3-apastel.tar.gz.
I went with that approach because I ended up having to modify that Dockerfile already anyway to fix a different bug. Had to change

ARG python_version=3.6.12

to

ARG python_version=3.7.0

because Python 3.6 is not compatible with a line in fbs/freeze/__init__.py:48 that uses the capture_output=True keyword argument in the line

cp = run(args, capture_output=True, text=True)

Now I'm able to build the VM, create the release, and install and run the app without any errors that are specific to fbs. (Just errors pertaining to Qt that could be separate.) It's still a little puzzling though that hacking open the tarball or hosting it on the internet somewhere is some undocumented required solution to get the Linux build working, especially considering this is not free software (did everyone have to do this same hack?). But I was able to successfully release a separate Windows application just fine at least, so it was still worth it for the Windows portion.

[apastel]

Fantastic, much appreciated. I forwarded my purchase receipt from August '22 to your email address.