rawhash | memory key : value cache | Runtime Evironment library

How about this modification?

For example, when the current script of your question is used, in the case that MD5(O2:O) is used as a custom function, input of function MD5(input) {} is 2 dimentional array like [[value of O2], [value of O3],,,]. But in your script, the result is returned by inputting a value which is not an array. By this, the error shown in your question occurs. So in order to input and output the array, the script is required to be modified for this situation as follows.

From what I know of base64_decode, it just works. Something must be wrong in your $rawHashes string. If you have line breaks in your string, you need to get rid of them by replacing them with an empty string. The hash that base64_decode needs should be one long line of base64 encoded string. It is not uncommon to receive a hash that is broken into multiple lines.

Try this ...

The compiler can't infer ivar types from the return type of method calls (like hash_value.as_h). The reference of Type inference lists all rules where the compiler can infer ivar types.

Infering the type from method calls is probably not impossible, but more complicated. It might come to the language at some point, but for now you'll have to use an explicit type annotation such as @hash_value : Hash(JSON::Any, JSON::Any).

You can pass the Byte[] array returned from the Utilities::computeDigest directly to a Utilities::base64EncodeWebSafe invocation. So you could do something like the following:

It sounds like you hit on the right approach with attempting to move the appendRow() call out of the loop. Anytime you are reading or writing to a spreadsheet you can expect the individual call to take 1 to 2 seconds, so this will eat up a lot of time when you get matches. Storing the matches in an array and writing them all at once is the way to go.

Another thing I notice is that your script calls getValues() in the actual for loop condition statement. The condition statement is executed each time on each iteration of the loop, so this is potentially wasting a lot of time even when you don't have matches.

A final tweak that may be helpful depending on your desired behaviour. You can stop the inner for loop after it finds the first match, which, if you only care about the first match or know there will only be one match, will save you a lot of iterations. To do this, put "break" immediately after the retreiveddata.push(masterdata[j]); line.

To fix the getValues issue, Change:

Please check data when you send payumoney for create hash key with server api data for create your hash key.