Workaround for compile error with Material Icon dependency

If you have recently installed Xojo or have invalidated the cache, you may be seeing this error when you try to run/build any Android project:

Unable to download Material Icon dependency required for building. Perhaps it is offline or there is an Internet connectivity problem. Please try again later.

We use an external dependency for the Material Icons that are used by Picture.SystemImage(). Although we knew the server responsible for that dependency (jcenter) was deprecated, we were unaware it was schedule to go offline on August 15th.

Since the dependency cannot be downloaded from that server, you’ll get a compile error. However, if you happened to use Xojo for Android before August 15th, it’s likely that this dependency is cached on your system so things will continue working.

If you’ve been impacted by this, please accept my apologies. This was entirely our (mostly my) fault and should have been caught sooner.

Workaround
We have identified an alternative server that can distribute the dependency, but it does require changes to some of the Android app’s configuration files.

This is fixed for 2024r3, of course, but in the meantime you can follow these steps to workaround this issue:

  1. Start Xojo if it is not running.
  2. Quit Xojo.
  3. On Windows/Linux, copy AndroidTemplate.zip to the Xojo Resources/Frameworks/Android in the Xojo folder. Do not unzip it. This will replace the file that is already there.
  4. On macOS, right-click on Xojo.app and select Show Package Contents. Copy AndroidTemplate.zip to Contents/Resources/Frameworks/Android. Do not unzip it. This will replace the file that is already there.
  5. Start Xojo and do a test run of an Android project.

AndroidTemplate.zip

Again, sorry for any trouble this has caused you.

3 Likes

Attempting to download the “AndroidTemplate.zip” file results in error

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<BucketName>xojo</BucketName>
<RequestId>tx00000000000000321210c-0066c3a6bf-4858cba9-nyc3a</RequestId>
<HostId>4858cba9-nyc3a-nyc</HostId>
</Error>
1 Like

Should be OK now.

Yes working now.

Easy enough to use work around until 2024R3
Don’t beat yourself up about it :grin:

1 Like

Thanks for this thread. I was going mad since searching on the Internet produced no result at all, as trying to update everything in Android Studio (which eventually came to a complete up to date state) and I have to make an Android app for the next week-end.
I’ve yet to try the workaround.
And don’t worry. Anyone do make mistakes and you solved the problem.

BTW: doesn’t step 4 cancel Xojo’s app signature?

Edit: the workaround has worked for me, thanks again.

1 Like