Buttercup-desktop: Error when adding meta

Created on 17 Nov 2017  路  12Comments  路  Source: buttercup/buttercup-desktop

When I try to add a custom field this error appears:

Unhandled Error
TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
    at d (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13448:2753)
    at s (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13448:1399)
    at Function.o.from (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13454:532)
    at Object.encodeStringValue (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13454:70036)
    at Object.wrap (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13454:75198)
    at i.addArgument (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13454:74667)
    at u.setMeta (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:13460:41426)
    at meta.forEach.metaObj (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:75731:13)
    at Object.updateEntry [as e] (file:///C:/Program%20Files/Buttercup/resources/app.asar/dist/main.bundle.js:75728:8)

But I can edit already created Fields without an error

Please Help me!

Windows High Bug

Most helpful comment

@BlueBeniHD I've fixed this error in my latest PR(#400). It's already merged and labeled with "Needs release".

All 12 comments

Hi @BlueBeniHD - Can you confirm that you're on the latest version? Please try a full restart of the application and try again, if you wouldn't mind. I can't reproduce this on Mac, so I wonder if what you're experiencing is a windows issue.

EDIT: Are you filling out the title and value?

@sallar The at u.setMeta seems to be when the meta is getting set.. Perhaps verification is failing here..?

At very least this error message shouldn't appear, so I'm marking this as a bug.

Hi, @perry-mitchell Yes I'm on the latest version v.0.24.1.
I'm on Windows, but on my Mac, there is the same issue.

Ok.. Let's see if we can't narrow this down. Could you please walk me through the exact steps you take to reproduce the error?

A video/gif recording of you recreating the issue would be extremely helpful also.

@perry-mitchell I'll be doing this, give me a minute.

@BlueBeniHD It's quite late here in Helsinki, so if I don't get a chance to look at this tonight I'll continue first thing.

@perry-mitchell Maby its important that I'm connected via OwnCloud.
I'm coming from Austria, it's also late here.

@BlueBeniHD I've fixed this error in my latest PR(#400). It's already merged and labeled with "Needs release".

@BlueBeniHD @perry-mitchell @ph1p We will release a new version today, we can close this after @BlueBeniHD can confirm that it's gone in that version. I'll update here when the version is out.

@perry-mitchell @sallar @ph1p in v0.24.2 the issue is fully gone, thank you for your quick support!

@BlueBeniHD glad to know :) closing this 馃憤

Was this page helpful?
0 / 5 - 0 ratings