toolkit-for-ynab: Chrome Extension Corrupts
Defective ToolKit Feature Name:
Expected Behavior
Actual Behavior
When I click on my pre-made nYNAB shortcut on my toolbar, it opens, loads, and I notice none of the Toolkit settings are activated. I got to the toolkit page and chrome and it says the extension is corrupt. I click repair, reload the nYNAB page, and it says it’s corrupt again.
Tried reinstalling the extension to no avail.
Steps to Reproduce the Behavior
- Open nYNAB
-
-
Export of Toolkit Settings (Bottom Left of Settings Page)
[{"key":"accountsClearSelection","value":true},{"key":"accountsDisplayDensity","value":"2"},{"key":"accountsEmphasizedOutflows","value":true},{"key":"accountsRowHeight","value":"0"},{"key":"accountsSelectedTotal","value":true},{"key":"accountsStripedRows","value":true},{"key":"activityTransactionLink","value":true},{"key":"betterScrollbars","value":"1"},{"key":"budgetBalanceToZero","value":true},{"key":"budgetProgressBars","value":"0"},{"key":"budgetQuickSwitch","value":false},{"key":"budgetRowsHeight","value":"1"},{"key":"calendarFirstDay","value":"0"},{"key":"categoryActivityPopupWidth","value":"2"},{"key":"changeEnterBehavior","value":true},{"key":"checkCreditBalances","value":false},{"key":"checkNumbers","value":false},{"key":"closeReconcileWindow","value":true},{"key":"collapseExpandBudgetGroups","value":true},{"key":"collapseSideMenu","value":true},{"key":"colourBlindMode","value":false},{"key":"compactIncomeVsExpense","value":true},{"key":"currentMonthIndicator","value":true},{"key":"daysOfBuffering","value":true},{"key":"daysOfBufferingHistoryLookup","value":"0"},{"key":"editButtonPosition","value":"2"},{"key":"enableRetroCalculator","value":true},{"key":"enlargeCategoriesDropdown","value":true},{"key":"enterInRegisterNow","value":true},{"key":"goalIndicator","value":true},{"key":"goalIndicatorWarningColor","value":true},{"key":"googleFontsSelector","value":"1"},{"key":"hideAOM","value":false},{"key":"hideHelp","value":true},{"key":"highlightNegativesNegative","value":true},{"key":"importNotification","value":"2"},{"key":"incomeFromLastMonth","value":"0"},{"key":"l10n","value":"0"},{"key":"largerClickableIcons","value":true},{"key":"monthlyNotesPopupWidth","value":"2"},{"key":"navDisplayDensity","value":"1"},{"key":"pacing","value":"0"},{"key":"popupCalculator","value":true},{"key":"printingImprovements","value":true},{"key":"privacyMode","value":"0"},{"key":"reconciledTextColor","value":"0"},{"key":"removePositiveHighlight","value":true},{"key":"removeZeroCategories","value":true},{"key":"reports","value":true},{"key":"resizeInspector","value":true},{"key":"rightClickToEdit","value":true},{"key":"runningBalance","value":true},{"key":"seamlessBudgetHeader","value":true},{"key":"showIntercom","value":true},{"key":"spareChange","value":false},{"key":"splitKeyboardShortcut","value":true},{"key":"splitTransactionAutoAdjust","value":true},{"key":"squareNegativeMode","value":true},{"key":"stealingFromNextMonth","value":true},{"key":"swapClearedFlagged","value":false},{"key":"toBeBudgetedWarning","value":true},{"key":"toggleSplits","value":true},{"key":"toggleTransactionFilters","value":"2"},{"key":"warnOnQuickBudget","value":true}]
System Settings
ToolKit Version: 1.0.0 Operating System (Mac/Windows/Etc): Ubuntu 16.04 Browser (Chrome/Firefox/Safari): Chrome Browser Version: Version 59.0.3071.86 (Official Build) (64-bit) Other Extensions: Nil
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 42 (8 by maintainers)
I’ve seen multiple reports of this being fixed now! I’m going to go ahead and close it. Please re-open if you guys still have issues on version 1.1.0!
Same here on Chrome OS, I tried deleting the extension, rebooting, and reinstalling the extension: no better. I will try downloading the file and unpacking. Thanks for your work on this! Limping along on plain nYNAB has been painful!
Thank you @stevesbrain, using your rebuilt plugin and everything works fine !
@stevesbrain I think it has to do with how Chrome is code signing the
.crxfile. When we upload into the extension store, we actually use an unsigned .zip file (which comes out as part of the build) and then they code sign that into the resulting.crx.My hypothesis is that Chrome is fiddling with some files when it expands the extension, which causes it to fail checksum verification, and they think it’s corrupt, and that the reason loading it unpacked works is because Chrome doesn’t verify checksums/signatures on unpacked extensions.
Unfortunately, if that’s the case, there’s no way to fix it properly from our side.
That being said, I already create unsigned copies of the extension for Chrome on each release here: http://toolkitforynab.com/desktop-updates/toolkitforynab_desktop.zip so whenever we push to the app store that’ll get updated. That’s being fed from our GitHub pages branch here: https://github.com/toolkit-for-ynab/toolkit-for-ynab/tree/gh-pages/desktop-updates so you can subscribe for updates and/or see the history / when that file was last updated.
@stevesbrain Works perfectly, thanks for the assistance!
@PteDefcon No worries at all! I’ve uploaded the built version, and you can grab it from here! sha256sum is:
Just keep in mind, as you’ll be loading an unpacked extension, Chrome will load it from that location on disk each time - i.e. don’t remove the files after loading them to Chrome 😃
EDIT: See comment by @blargity below to grab the official unsigned builds.
Here’s one for you. Standard Chrome extensions page. I did test this in Incognito with only Toolkit enabled, and it still crashed. I have https://app.youneedabudget.com/ as my bookmark, and it crashes before the URL change for loading the budget occurs.