> On Feb 8, 2018, at 9:52 AM, David T. via gnucash-user 
> <gnucash-user@gnucash.org> wrote:
> 
> In thread 
> https://lists.gnucash.org/pipermail/gnucash-user/2018-January/074224.html 
> <https://lists.gnucash.org/pipermail/gnucash-user/2018-January/074224.html>, 
> I noted that after upgrading my installation from 2.6.16 to 2.6.19 on my Mac 
> (OS X 10.13.3), Price retrieval was failing with the generic error: "There 
> was an unknown error while retrieving the price quotes.”
> 
> *** As I noted there: Finance::Quote works at the command line:
> 
> $ /Applications/Gnucash.app/Contents/Resources/bin/gnc-fq-check
> ("1.47" "adig" "aex" "aiahk" "alphavantage" "amfiindia" "asegr" "asia" "asx" 
> "australia" "bamosz" "bet" "bmonesbittburns" "bourso" "brasil" "bse" "bsero" 
> "canada" "canadamutual" "citywire" "cominvest" "cse" "deka" "dutch" 
> "dwsfunds" "europe" "fetch_live_currencies" "fidelity" "fidelity_direct" 
> "fidelityfixed" "financecanada" "finanzpartner" "finland" "fool" "france" 
> "ftfunds" "ftportfolios" "ftportfolios_direct" "fundlibrary" "goldmoney" 
> "greece" "hex" "hu" "hufund" "hungary" "hustock" "indiamutual" 
> "known_currencies" "lerevenu" "maninv" "morningstar" "morningstarjp" 
> "mstaruk" "nasdaq" "nyse" "nz" "nzx" "platinum" "romania" "seb_funds" 
> "sixfunds" "sixshares" "stockhousecanada_fund" "tdefunds" "tdwaterhouse" 
> "tiaacref" "tnetuk" "troweprice" "troweprice_direct" "trustnet" "tsp" "tsx" 
> "uk_unit_trusts" "ukfunds" "unionfunds" "usa" "usfedbonds" "vanguard" "vwd" 
> "yahoo" "yahoo_asia" "yahoo_australia" "yahoo_brasil" "yahoo_europe" 
> "yahoo_json" "yahoo_nz" "yahoo_yql" "za" "za_unittrusts”)
> 
> $ /Applications/Gnucash.app/Contents/Resources/bin/gnc-fq-dump -v 
> alphavantage AAPL
> Finance::Quote fields Gnucash uses:
>    symbol: AAPL                 <=== required
>      date: 02/08/2018           <=== recommended
>  currency: USD                  <=== required
>      last: 160.1350             <=\       
>       nav:                      <=== one of these
>     price:                      <=/        
>  timezone:                      <=== optional
> 
> *** As I noted earlier: I restored the following two lines to 
> /Applications/Gnucash.app/Contents/Resources/etc/gnucash/environment:
> 
> # Set AlphaVantage API Key to allow Finance::Quote to work
> ALPHAVANTAGE_API_KEY=************8SET
> 
> It seems to me that somehow Gnucash.app is not reading or using the 
> ALPHAVANTAGE_API_KEY that is stored in its environment file. Either that, or 
> somehow my environment file is not properly configured. However, I do not see 
> any way to test these hypotheses. 
> 
> Can anyone tell me how I might determine **FROM WITHIN GNUCASH.APP** whether 
> the Alphavantage API key is being read, and what its value currently is? Is 
> there any other way to troubleshoot this problem?
> 
> David

Depending on your holdings, I’d suggest you open every single security in the 
security editor dialog and make sure that _none_ of them are set to retrieve 
online quotes from yahoo.

Back when my investing time horizon was a few months rather than years, I 
bought and sold stocks in a total of something like 200 companies. When the 
yahoo quote retrieval apocalypse hit, it took me three trips through the list 
of 200 companies to find the last stock that was set to use yahoo as a source. 
That’s annoying when one has to open each security definition individually to 
see if it is set to retrieve quotes and from where. Hmm, time for an 
enhancement request to include online-quote-source in the security editor main 
dialog list…

Dave
--
Dave Reiser
dbrei...@icloud.com





_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to