jEveAssets 4.5.0 Release Candidate 1 released
EDIT: 4.5.0 Stable Released
1 Like
jEveAssets 4.5.0 released
New Features:
-Support for ESI characters (shorter cache times, with a few exceptions)
-Update ESI/EveKit/EveAPI in threads (faster updates)
-Added support for evemarketer.com as a price source
Code:
-Completely new data backend with support for EveAPI/EveKit/ESI
Most ESI character endpoints have reduced cache time (compared to the XML API):
-Asset: 1 hour (was 6 hours)
-Account Balance: 2 minutes (was 15 minutes)
-Blueprints: 1 hour (was 12 hours)
-Contracts: 5 minutes (was 1 hour)
-Industry Jobs: 5 minutes (was 15 minutes)
Two ESI character endpoints had the cache time increased:
-Journal: 1 hour (was 30 minutes)
-Transactions: 1 hour (was 30 minutes)
2 Likes
jEveAssets 4.5.1 released
Bug Fixes:
-Fixed Market orders duplicates
-Fixed transactions fail to convert float to integer
-Fixed NPE in ProfileWriter (BugID: 539)
-Fixed NPE in AbstractEsiGetter
-Fixed NPE in MyIndustryJob (BugID: 541)
-Possible fix to NPE in UpdateTask (BugID: 540)
-Possible fix for universe/names errors (BugID: 542)
Code:
-Updated eve-esi library to 1.4.1
1 Like
Is there anything I need to do to make my characters “ESI characters”?
When I update it gives me warnings that the characters can be migrated and I still get the 6 hour assets timer.
When I go into the Accounts window I see the migrate button but when I click it all the options are greyed out and ‘OK’ changes nothing.
Edit: I figured it out. Had to use the ‘Add’ button and go through SSO auth for each character on each account, and then use the ‘Migrate’ buttons. Corporations cannot be migrated to ESI yet.
@Johann_Hemphill
Good job figuring it out yourself 
Any suggestions to make process easier to understand?
Yerh, no corporation ESI accounts, yet, It will be done soon, though. Maybe already next week, with a bit of luck. All the endpoints are done, but, the corp assets endpoint have a bug (not returning all assets), that needs to be fixed first.
@All
I’m sorry for the instability of the latest jEveAssets releases. I’m working as fast as I can to fix everything and I won’t stop until jEveAssets is as stable as it used to be.
1 Like
Not easy to go through every character on every account to repopulate lol. That would be a CCP thing. Best way I found was the click cancel once you’re done with an account and that will clear your login and allow you to select you next account quicker.
Yerh the SSO site could be more user friendly. But, there is a GitHub repo with SSO issues now, so, we all hope it will get better with time. The SSO team is not the same as the ESI team. The SSO team also handles a lot of internal CCP issues and are apparently super busy all the time.
1 Like
Somehow I got the impression that “can be migrated to ESI” implied “will automatically be converted to ESI”. A line of instructions in the release notes would have done it for me. And a section on migration in the README. And a more detailed warning in the Update window which is where most folks are probably going to notice it. I first checked all over the CCP Support site to see if there was an option to switch my accounts to ESI because it was un-intuitive to me that I had to re-add the characters in Accounts, even though the message was clear enough in retrospect.
1 Like
Thank you for your feedback … I will try to include that in the next bug fix version
1 Like
Just converted all of my characters to ESI and discovered one issue:
Looks like ships that are not docked are not covered in the asset list. This is problematic for supers that are sometimes docked and sometimes not where total assets fluctuate massively. It also doesn’t pick up anything stored in the supers etc. so when moving ships, they also disappear out of assets.
Is this a limitation of ESI or is it something that can be fixed?
That is a limitation of ESI.
If you like, you can add your voice to the ESI GitHub issue
1 Like
Will do, thank you for the reply
jEveAssets 4.5.2 released
Bug Fixes:
-Fixed missing names
-Updated BPO/BPC detection code
-Better error handling for update threads
-Better handling of cancel while updating
-Better ESI error limit support
-Made RawConverter thread safe
-Better ESI migration warning
1 Like
jEveAssets 5.0.0 released
New Feature:
-Support for ESI Corporation accounts
Bug Fix;
-Fixed missing names (BugID: 542, 544, 546)
-Fixed the compatibility issue with Java 9 (BugID: 545, 547)
-Possible fixed for NPE in JContractsTable (BugID: 551)
-A few minor bug fixes
Code:
-Better error handling (again)
3 Likes
I’m loving these shorter cache times. One question: I’ve noticed that the data pulled from the API is not real time data. I’m in the habit of avoiding placing big orders or moving items around for an hour before an update to ensure nothing gets counted twice. Any idea whether this has changed with ESI?
@Johann_Hemphill
If you update no more than once every hour via ESI, you should get a complete snapshot of everything, as no ESI endpoints have more than 1 hour cache time.
If you update more often than that, stuff may be inaccurate, as assets now in sell orders or contracts, may still be in assets, effectively being counted twice.
Additional, if your active ship is in space at the time of update, that will not be included in your assets. This is to avoid intel leaks via the assets endpoint. ATM. stuff fitted to your active ship in space is included, but, that may or may not change in future - once a decision have been made, I may include the active ship via the location endpoints, that allow you to get your active ship and location.
I’m pretty sure all data should be current when you update from the API. If you’re able to reproduce this in ESI, you should let me know, so, I can create an issue for it.
1 Like
I’m a dedicated user of jEVEAssets, and I’'m happy to see the new version including ESI support.
But I am getting a consistent error when I update my data:
ESI>Contract Items>[corp name]
Error Code 420
Can you help remedy this problem?
@Mollie_Athonille
Thank you for your bug report
To debug this I need the logs: How to send a bug report
I will look into it as soon as I have the logs…
1 Like
actually I got two problems;
1st is; all my assets are getting listed twice (added ESI , migrated and deleted the old API’s)
2nd; all learned skills on my characters are getting listed as asset, but it shouldn’t or is this working as intended?
Thanks for your answer in advance!
@ReacT1337
Thank you for your bug report
- Terrible bug
A quick look at the code confirms the bug - That have already been reported and the fix have been committed to GitHub.
Both fixes will be included in the next release (I hope to release it this weekend)
EDIT: I’m not able to reproduce the first bug, but, I will try to look into it today
2 Likes