Code signing error ("object file format unrecognized, invalid, or unsuitable") in Game Salad IPA - ipa

We are using GameSalad to develop games for iOS. we have developed one app and while generating IPA we are getting below error.
We have same error while uploading application:
Code Signing Error 1: /var/folders/gp/_32pgwv96m1gsyj88zcvqpb40000gn/T/GameSalad1/1/TTH_V2.app: replacing existing signature codesign_allocate: object: /private/var/folders/gp/_32pgwv96m1gsyj88zcvqpb40000gn/T/GameSalad1/1/TTH_V2.app/TTHV2 malformed object (unknown load command 41) /var/folders/gp/_32pgwv96m1gsyj88zcvqpb40000gn/T/GameSalad1/1/TTH_V2.app: object file format unrecognized, invalid, or unsuitable
Make sure your provisioning profile, developer certificate, and WWDR certificate are installed, valid, not expired or duplicated, and signed with a private key in the keychain on the computer you are signing with.
Mac version : 10.8.5 x-code : 5.1.1 Gamesalad version : 0.11.0.14 beta

Whilst this might not be ideal, if you can get hold of the IPA you can manually sign it with a mac application called iRe-Sign - always does a great job. It's available here:
https://github.com/maciekish/iReSign

Related

How fix error "Incorrect magic number" on wordpress generate voucher PDF?

platform: wordpress + woocommerce + PDF Product Vouchers
When generating a voucher, an error sometimes pops up:
could not generate voucher pdf: cannot create voucher: incorrect magic number (0)
What could be the problem?
You're getting this error because your hosting server has an incorrect SSL certificate set for OpenSSL, so when this third-party library dompdf (which is being used by SkyVerge) sends a file_get_contents() request to this URL to load Google fonts, it throws this error SSL: Connection reset by peer.
The quick solution to fix it is to put this snippet below in your functions.php or any code snippet plugin like WPCode, which will unload Google Fonts and use the default fonts:
add_filter('wc_pdf_product_vouchers_available_google_fonts', function(){
return [];
});
If you mean Skyverge product, it's actual issue. Skyverge is looking for a solution. But if ASAP, then try to replace with PDF plugin version 3.8, not 3.9 and newer.
The problem was caused by the plugin: mail log. After disabling, everything works without errors.
Probably the problem is in the incorrect function of sending letters.

passport-apple inexplainable invalid_client on nodejs backend -- using clean example repository with fresh set of credentials

I've cloned https://github.com/ananay/passport-apple-example and replaced the config with this:
clientID: "com.myname.web",
teamID: "myteamid",
callbackURL: "https://myurldev.com/auth/apple/redirect",
keyID: "mykeyid",
privateKeyLocation: path.join(__dirname, "../apple-key.p8")
I've also added SSL certificate on my machine and starting the server with https, all works fine & is recognized by my browser. I'm also starting the app on port 443 and proxying using my hosts file myurl.dev.com -> 127.0.0.1.
I have the same auth setup for facebook, google & microsoft and everything works fine.
I have:
Created a new APP identifier and enabled Sign in with Apple for it, named it: com.myname.dev
Created a new SERVICE identifier and enabled Sign in with apple, called it: com.myname.web
Added "https://myurldev.com/auth/apple/redirect" to the "Reply URLS" on the service identifier com.myname.web
Set my app identifier com.myname.dev as the main app identifier my service to be grouped with.
Created a private key and enabled sign in with apple, interface confirmed the presence of grouped ID com.myname.web bundled with com.myname.dev for which the key was created.
I have confirmed using console.log that the private key is indeed at the path being passed as parameter.
converted the .p8 file to base64 & then back to UTF-8 in an attempt to use the string for privateKeyString
successfully implemented Apple Oauth several times in the past using passport-apple
This time around, for some reason, auth simply doesn't work.
If I set the clientID as the APP identifier, not the service, I'm getting
invalid_request
Invalid web redirect url.
instead of invalid_client
Any advice on debugging this is highly appreciated. Thank you.
EDIT #1:
I have dug a bit deeper into the passport-apple package to figure out if anything goes against apple's docs around token generation, but the flow never reaches that part, indicating things go wrong on the actual configuration in Apple's console & what I'm trying to use for my project.
EDIT #2
2 of the app Ids I have created always throw "wrong redirect uri" because they're not service IDs so I can't configure redirect_uri, this will change if to "required" if I pass undefined as a redirect_uri.
One of the app ids throws only invalid client_id instead, regardless if I pass undefined or good value for redirect_uri.
EDIT #3
Went full vanilla through the OAuth code flow process and just created a url & redirected the user it, failing with this method is consistent with what is happening when using the passport-apple module.
const url = new URL("https://appleid.apple.com/auth/authorize");
url.searchParams.append("state", "fdbd287b1f");
url.searchParams.append("response_type", "code");
url.searchParams.append("scope", "name email");
url.searchParams.append("response_mode", "form_post");
url.searchParams.append(
"redirect_uri",
"https://raiseitupdev.com/auth/apple/redirect",
);
url.searchParams.append("client_id", "com.myname.web");
return res.redirect(url.toString());
[Creator of the library here.]
Did it stop working in development too? I feel this is a configuration error because the actual thing is working live on my website:
https://passport-apple.ananay.dev
Please follow up on this Github issue. Thanks!
https://github.com/ananay/passport-apple/issues/23

Using SSL with the python-instagram and localhost on sample-app.py

I plan on using the sample-app.py as a baseline of what I am building out and then expanding it from there. Just want to get comfortable with the instagram API and build out from there.
I am trying to use the sample-app.py provided with python-instagram. I have registered an application on instagrams website. I set it up using the default redirect uri from sample-app.py:
http://localhost:8515/oauth_callback .
I was able to authorize my instagram account to use the app, but when I click on any of the links, I get an error about the acccess-token.
When you look at the python command-line window that stays open, I get the following error:
"check_hostname needs a SSL context with either CERT_OPTIONAL or CERT_REQUIRED"
It appears that when the sample app is processing the lines below, it is trying to connect to instagram, but is not able to because SSL in local host is not set up properly. How do I set up SSL so i do not get the above error?
access_token, user_info = unauthenticated_api.exchange_code_for_access_token(code)
if not access_token:
return 'Could not get access token'
api = client.InstagramAPI(access_token=access_token)
request.session['access_token'] = access_token
print ("access token="+access_token)
There are a few steps to solve this problem (it appears that it is actually several problems in aggregate causing this issue):
use openssl to create a ssl certificate and save cert to the same location as your python script. Download open ssl here: http://slproweb.com/products/Win32OpenSSL.html
You need to tweak bottle so that it will support ssl. Do so by adding the following lines in run in class WSGIRefServer(ServerAdapter):
import ssl
srv.socket = ssl.wrap_socket (
srv.socket,
certfile='server.pem', # path to certificate
server_side=True)
There is a bug in python 3 and above(https://github.com/jcgregorio/httplib2/issues/173). I am using 3.4, so the bug could be fixed in 3.5. In the instagram/oauth2.py file, change all disable_ssl_certificate_validation=False to True.

How do I find the Google's OAuth 2.0 client-secret-key for developing chrome-extensions?

I see only the following details in
https://code.google.com/apis/console/b/0/#project:xxxxx:access
Client ID for installed applications
Client ID: 477522346600.apps.googleusercontent.com
Application type: Chrome App
Application ID: gobkdpbocikdfbnfahjladnetpdkvmic
Simple API Access
API key: AIzaSyDC_BSfqa1Uhgh3M6KqYUvzXuKX0lMnMaw
Referers: Any referer allowed
Activated on: Mar 21, 2013 4:35 AM
Activated by: xxx#yyyy.com – you
Now, what's my client-secret value in the above data?
OK, figured it out by myself.
Click the Download JSON link in the Client ID for installed applications section.
Open the JSON in a text-file.
You will find the client-secret.
On Credentials page,
place cursor over Name (Name is not underlined without cursor over it)
once Name is highlighted and underlined, click.
For credentials with Chrome App you won't get a client_secret only the client_id. I suggest creating it as type other instead. This should give you an ID and a secret you can use for your extension.
In case if anyone will step into thi misunderstanding like I did.
If you create OAuth client with Application type "android" (and Chrome App as #Erich answered) you won't get client secret.
Use this (picture) instructions to acquire the key.

Prob in testing Blackberry App in device: Secure API prob

I have developed a Blackberry app in Blackberry JDE. It is working fine in simulator. As I have used different API which need signing key, I try it to 'Signature Tool' so that I can run it in device. Initially the Signature Tool was showing like below.
When I 'Request' for signature, all the row having 'Not Signed' status, successfully converted to 'Signed'.
Now when I install the app in my Blackberry device and try to run it, it gives massage "Error starting Certainteed: Module 'Certainteed' attempts to access a secure API.". I think this massage should come only for not signed Cod file. Is there any problem in my signing process?
N.B. I am using Blackberry JDE 4.6 and Blackberry Curve 8520 (software version 4.6.1.286)
It looks to me as if you haven't installed all of your signing keys, only the RBB signing key.
When you requested your signing keys you should have received 3 emails in response, each containing a different signing key:
client-RBB-xxxxxxxxx.csi
client-RCR-xxxxxxxxx.csi
client-RRT-xxxxxxxxx.csi
You need to install all 3 keys

Resources