Adie Member Licensed User Longtime User Dec 19, 2017 #1 Hi I get the following error during compile of the sample. I did try with DBUtils V2.02 B4X: B4A Version: 7.80 BETA #1 Parsing code. (0.04s) Compiling code. (0.08s) Compiling layouts code. (0.00s) Organizing libraries. (0.00s) Generating R file. Error ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:font ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontStyle ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontWeight Adie
Hi I get the following error during compile of the sample. I did try with DBUtils V2.02 B4X: B4A Version: 7.80 BETA #1 Parsing code. (0.04s) Compiling code. (0.08s) Compiling layouts code. (0.00s) Organizing libraries. (0.00s) Generating R file. Error ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:font ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontStyle ERROR: In <declare-styleable> FontFamilyFont, unable to find attribute android:fontWeight Adie
Erel B4X founder Staff member Licensed User Longtime User Dec 20, 2017 #2 You should update Android SDK. Use the new embedded tool. https://www.b4x.com/android/forum/threads/b4a-v7-80-beta-has-been-released.87207/#post-551921 Upvote 0
You should update Android SDK. Use the new embedded tool. https://www.b4x.com/android/forum/threads/b4a-v7-80-beta-has-been-released.87207/#post-551921
Adie Member Licensed User Longtime User Dec 20, 2017 #3 Have done that. Downloaded the latest SDK tools from the link. Ran the SDK Manager again from within B4A. Only Intel Atom TV not installed. (All Maven done) Still no luck with DBUtils. My own little app compile an run fine. Upvote 0
Have done that. Downloaded the latest SDK tools from the link. Ran the SDK Manager again from within B4A. Only Intel Atom TV not installed. (All Maven done) Still no luck with DBUtils. My own little app compile an run fine.
Erel B4X founder Staff member Licensed User Longtime User Dec 20, 2017 #4 Have you configured B4A to use the new SDK (android.jar path)? Can you upload the project? Upvote 0
Adie Member Licensed User Longtime User Dec 20, 2017 #5 THANKS The problem was the B4A Path. Still pointed to 25. btw. the project was the standard DBUtils Upvote 0