How to force jar resolver to use v26+ android support libraries, it's resolving old v25.3.1 files?!

Hi there,

When I use the latest jar resolver which now comes packaged with updated prime31 plugins, the resolver is finding older versions of the android support library files like: support-v4-25.3.1, when it should be v26+ Does anyone know what dictates this? and how to force it to use a new version. My app fails to create a usable build using the older support files.

If I toggle between the old resolver and the new, the old resolver gives me the desired v26+ support libraries, however it's not an actual viable option for me to use the older resolver, some other dependencies that the updated prime31 plugins require are then missing.

I've relayed all of this to support at Prime31, will post results if I get an answer, but hoping someone here knows how to coax the new resolver to work as desired.

Thanks!

 

I feel like I may have found a bit of a clue about what's happening. I dug in to my installed android SDK to see if I could find anything. I searched for support-v4 and found the file maven-metadata.xml which has this old 25.3.1 version set as the release version?! (shown below) This is the version that the new jar resolver is using and seems to be the cause of my issue. But I don't know how to force this support library to be setting newer 26+ versions as the release version to use. I uninstalled the support library, sdk tools, platforms tools, hoping that the SDK manager had broken somewhere along the line, I then reinstalled them and the same files/settings have come back. I'm trying to figure out what dictates this version to be set... any chance this has made it obvious to anyone what's going wrong? thanks.

Code (CSharp):

1. <?xml version="1.0" encoding="UTF-8"?>
2. <metadata>
3.   <groupId>com.android.support</groupId>
4.   <artifactId>support-v4</artifactId>
5.   <versioning>
6.     <release>25.3.1</release>
7.     <versions>
8.       <version>13.0.0</version>
9.       <version>18.0.0</version>
10.       <version>19.0.0</version>
11.       <version>19.0.1</version>
12.       <version>19.1.0</version>
13.       <version>20.0.0</version>
14.       <version>21.0.0</version>
15.       <version>21.0.2</version>
16.       <version>21.0.3</version>
17.       <version>22.0.0</version>
18.       <version>22.1.0</version>
19.       <version>22.2.0</version>
20.       <version>22.2.1</version>
21.       <version>23.0.0</version>
22.       <version>23.0.1</version>
23.       <version>23.1.0</version>
24.       <version>23.1.1</version>
25.       <version>23.2.0</version>
26.       <version>24.0.0-alpha1</version>
27.       <version>23.2.1</version>
28.       <version>23.3.0</version>
29.       <version>24.0.0-alpha2</version>
30.       <version>23.4.0</version>
31.       <version>24.0.0-beta1</version>
32.       <version>24.0.0</version>
33.       <version>24.1.0</version>
34.       <version>24.1.1</version>
35.       <version>24.2.0</version>
36.       <version>24.2.1</version>
37.       <version>25.0.0</version>
38.       <version>25.0.1</version>
39.       <version>25.1.0</version>
40.       <version>25.1.1</version>
41.       <version>25.2.0</version>
42.       <version>25.3.0</version>
43.       <version>26.0.0-alpha1</version>
44.       <version>25.3.1</version>
45.     </versions>
46.     <lastUpdated>20170322231652</lastUpdated>
47.   </versioning>
48. </metadata>

 

This issue seems to be actual still. Did you find a solution?

 

The issue is still here.