For the query “unable to find an exact match for cdp version 115, so returning the closest version found: 111”, the system couldn’t find an exact match for the requested CDP version of 115. However, it found a closest version which is 111 and is returning that as the result.
Here’s an example to illustrate this scenario:
CDP versions available:
- Version 110
- Version 111
- Version 112
- Version 113
- ...
- Version 120
Requested CDP version: 115
Since an exact match for version 115 is not found, the system checks for the closest available version. In this case, the closest version is 111. Therefore, the system returns version 111 as the result.
Related Post
- Could not locate aapt. please ensure you have the android buildtools installed.
- Attributeerror: ‘upsample’ object has no attribute ‘recompute_scale_factor’
- Typeerror: failed to execute ‘createobjecturl’ on ‘url’: overload resolution failed.
- Unable to evaluate the expression method threw ‘org.hibernate.lazyinitializationexception’ exception.