search

bkper / bkper-issues

Feature requests and enhancements to existing bkper modules can also be filed here.
https://bkper.com/
2 stars 0 forks source link

Cannot open BKper from Google Sheet #31

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I cannot seem to open the Bkper side panel from Google Sheets anymore. Each 
time I open from Google Sheets Add-on for Bkper under "open", the Bkper side 
panel fires up but it is blank after that and not showing anything any more.

Before I could export transactions. Now, I cannot see anything at all.

Please see enclosed file.

Thanks.

Original issue reported on code.google.com by tre...@glocalex.com on 11 Jul 2015 at 1:02

GoogleCodeExporter commented 8 years ago 
Hi,

Is your Chrome version 44 Beta? If so, there is a known Issue the Chrome team 
is already working on:

http://help.bkper.com/article/14-issue-tracker

If not, could you please copy and pase the JavaScript console output?

Original comment by m...@nimbustecnologia.com.br on 11 Jul 2015 at 1:53

GoogleCodeExporter commented 8 years ago 
My version is Version 45.0.2453.0 canary (64-bit). Let me look at generating 
the Javascript console output.

Original comment by tre...@glocalex.com on 11 Jul 2015 at 4:19

GoogleCodeExporter commented 8 years ago 
SES initialization
ses-single-frame.opt.js?debug=1:43  Repaired: Non-deletable RegExp statics 
are a global communication channel
ses-single-frame.opt.js?debug=1:43  Repaired: Date.prototype is a global 
communication channel
ses-single-frame.opt.js?debug=1:43  Not repaired: Number.prototype should be 
a plain object
ses-single-frame.opt.js?debug=1:43  Not repaired: Boolean.prototype should 
be a plain object
ses-single-frame.opt.js?debug=1:43  Not repaired: String.prototype should be 
a plain object
ses-single-frame.opt.js?debug=1:43  Not repaired: RegExp.prototype should be 
a plain object
ses-single-frame.opt.js?debug=1:43  Not repaired: %ThrowTypeError% has 
normal function properties
ses-single-frame.opt.js?debug=1:43  Max Severity: Safe spec violation(1).
ses-single-frame.opt.js?debug=1:43  18 Cannot be 
poisonedses.logger.console.undefined.log.forward @ 
ses-single-frame.opt.js?debug=1:43error @ 
ses-single-frame.opt.js?debug=1:45defaultReportDiagnosis @ 
ses-single-frame.opt.js?debug=1:51(anonymous function) @ 
ses-single-frame.opt.js?debug=1:658logReports @ 
ses-single-frame.opt.js?debug=1:658ses.startSES @ 
ses-single-frame.opt.js?debug=1:677hookupSESPlusModule @ 
ses-single-frame.opt.js?debug=1:695(anonymous function) @ 
ses-single-frame.opt.js?debug=1:695
ses-single-frame.opt.js?debug=1:43  232 Deleted
ses-single-frame.opt.js?debug=1:43  215 Frozen harmless
ses-single-frame.opt.js?debug=1:43  1 Skipped
ses-single-frame.opt.js?debug=1:43  6 unexpected 
intrinsicses.logger.console.undefined.log.forward @ 
ses-single-frame.opt.js?debug=1:43error @ 
ses-single-frame.opt.js?debug=1:45defaultReportDiagnosis @ 
ses-single-frame.opt.js?debug=1:51(anonymous function) @ 
ses-single-frame.opt.js?debug=1:658logReports @ 
ses-single-frame.opt.js?debug=1:658ses.startSES @ 
ses-single-frame.opt.js?debug=1:677hookupSESPlusModule @ 
ses-single-frame.opt.js?debug=1:695(anonymous function) @ 
ses-single-frame.opt.js?debug=1:695
ses-single-frame.opt.js?debug=1:43  Max Severity: Not isolated(5) is not 
suitable for SES.ses.logger.console.undefined.log.forward @ 
ses-single-frame.opt.js?debug=1:43error @ 
ses-single-frame.opt.js?debug=1:45defaultReportMax @ 
ses-single-frame.opt.js?debug=1:50ses.startSES @ 
ses-single-frame.opt.js?debug=1:677hookupSESPlusModule @ 
ses-single-frame.opt.js?debug=1:695(anonymous function) @ 
ses-single-frame.opt.js?debug=1:695
ses-single-frame.opt.js?debug=1:43  initSES 
failed.ses.logger.console.undefined.log.forward @ 
ses-single-frame.opt.js?debug=1:43error @ 
ses-single-frame.opt.js?debug=1:45ses.startSES @ 
ses-single-frame.opt.js?debug=1:677hookupSESPlusModule @ 
ses-single-frame.opt.js?debug=1:695(anonymous function) @ 
ses-single-frame.opt.js?debug=1:695
ses-single-frame.opt.js?debug=1:555 Uncaught Error: SES not supported, 
aborting taming frame initialization.FakeError @ 
ses-single-frame.opt.js?debug=1:555(anonymous function) @ 
ses-single-frame.opt.js?debug=1:696
es53-guest-frame.opt.js?debug=1:198 Uncaught TypeError: 'caller' and 
'arguments' are restricted function properties and cannot be accessed in 
this context.DefineOwnProperty___ @ 
es53-guest-frame.opt.js?debug=1:198(anonymous function) @ 
es53-guest-frame.opt.js?debug=1:227(anonymous function) @ 
es53-guest-frame.opt.js?debug=1:422
es53-taming-frame.opt.js?debug=1:198 Uncaught TypeError: 'caller' and 
'arguments' are restricted function properties and cannot be accessed in 
this context.DefineOwnProperty___ @ 
es53-taming-frame.opt.js?debug=1:198(anonymous function) @ 
es53-taming-frame.opt.js?debug=1:227(anonymous function) @ 
es53-taming-frame.opt.js?debug=1:422

I am using Version 45.0.2454.0 canary (64-bit)

Thanks.

Original comment by tre...@glocalex.com on 11 Jul 2015 at 4:46

GoogleCodeExporter commented 8 years ago 
Thanks for the additional information.

We were able to reproduce the bug on Canary version. Its the same bug described 
in the Known Issue, and on Google Apps Script issues: 

https://code.google.com/p/google-apps-script-issues/issues/detail?id=5116

The bug seems to be fixed and will be rolled out on next days.

Meanwhile, a possible workround is to use a previous version of Chrome or 
Firefox (arg).

We really apologize the inconvenience and thank you once more for your report.

Original comment by m...@nimbustecnologia.com.br on 12 Jul 2015 at 12:13