Hello Michael,
You do not need Xcode for this, but you do need the command line tools. Try
typing this in a Terminal:
sudo xcode-select --install
This will install/update the missing command line tools.
Hope this helps.
Kind regards,
Panos
--
On Thu, 15 Oct 2020 at 02:01, Michael Lew via use-
Peter, thank you for the information about changing the scale of the
IDE user interface.
You mentioned that if I put a script somewhere to affect the IDE
stacks that it should work. I looked up the IDE stacks as per your
directions. Thanks for those.
I do not know where a good somewhere to p
I'm trying to build standalones from 9.6.1 business and cannot get the Mac
version to succeed. The process goes through the normal lot of "saving" and
"building" bits but it eventually turns up an alert that says
"There was an error while saving the standalone application
Adding the ad-hoc signa
On 10/14/20 11:18 AM, Ralph DiMola via use-livecode wrote:
I just got this message when submitting a new app to the PlayStore
Your APK is only signed using the APK v1 signature scheme. This will fail to
install in versions of Android equal or higher to 11 if the
android:targetSdkVersion is set
Good question. I'm not 100% sure, but if I'm correct you can update. So I
don't think the keypair will change. I've not had the error you have, and
I've updated with lc961 which uses the correct target. So i made the normal
keystore and did the thing as in the previous mail and had no problems as
f
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
Phone: 518-636-3998 Ex:11
Cell: 518-796-9332
Thanks!
One interesting thing is that keytool requires the keystore and the alias
passwords to be the same. I had them as different. Although you can change
the alias p
UPDATE:
Apple just released BigSur public beta 10 today and it’s back to printing OK
for me here. So the issue was apparently with Apple. Anybody want to check on
your end to confirm?
Marty
> On Oct 14, 2020, at 11:34 AM, Marty Knapp wrote:
>
> This BigSur printing bug happens when you "open
I think you need to use PKCS12 industry standard format instead of the
normal keystore. You can import your existing key via command prompt.
Keytool -importkeystore -srckeystore yourapp.keystore -destkeystore
yourapp.keystore -deststoretype pkcs12
Op wo 14 okt. 2020 18:17 schreef Ralph DiMola via
This BigSur printing bug happens when you "open printing with dialog” and has
been confirmed by Panos. Drop the “with dialog” and you can print. I don’t know
at this point if the issue is with LC or with Apple. In the event that it
doesn’t get fixed by the time BigSur is released, I want to have
I just got this message when submitting a new app to the PlayStore
Your APK is only signed using the APK v1 signature scheme. This will fail to
install in versions of Android equal or higher to 11 if the
android:targetSdkVersion is set to 30 or higher. Please use apksigner to sign
your APK or s
Apple has already provided a way forward for this. Their current best practice
is for apps to store files in their Documents folder in iCloud. This provides
seamless access between multiple devices and data security since it is not tied
to the app remaining installed.
I briefly looked at the
Indeed. The joy of web services integration projects - sometimes there are more
standards and variations of words than characters in a crime drama! :)
Best,
Keith
> On 14 Oct 2020, at 12:25, Tore Nilsen via use-livecode
> wrote:
>
> You should not be to embarrassed. There is a particular reaso
You should not be to embarrassed. There is a particular reason why I spotted
this. I think we have all been there at one time or another.
Best regards
Tore
> 14. okt. 2020 kl. 13:22 skrev Keith Clarke via use-livecode
> :
>
> Oh, dear - that's embarrassing! Thanks Tore - time to take a break a
Oh, dear - that's embarrassing! Thanks Tore - time to take a break and check
for updates on my eyeball firmware! :-D
Best,
Keith
> On 14 Oct 2020, at 12:04, Tore Nilsen via use-livecode
> wrote:
>
> In the url itself you use access_token but in your search you use
> access_code. May this be t
In the url itself you use access_token but in your search you use access_code.
May this be the reason for your problems?
Best regards
Tore Nilsen
> 14. okt. 2020 kl. 13:00 skrev Keith Clarke via use-livecode
> :
>
> Hi folks,
> Am I misreading the docs and abusing the 'is in' logic or syntax h
Hi folks,
Am I misreading the docs and abusing the 'is in' logic or syntax here...?
In my test case, the browser widget URL takes the form (truncated)
https://somewhere.com/callback.lc#access_token=0123456789&;...
This is visible in the field "ResponseURL" but the if statement is not firing.
I
Hello David,
Have you tried trashing your Prefs?
1. Quit LC
2. Delete files:
/Users//Library/Preferences/RunRev/livecode.rev
/Users//Library/Preferences/RunRev/livecode7.rev
3. Open LC
I hope this fixes the problem :)
Kind regards,
Panos
--
On Wed, 14 Oct 2020 at 01:10, David Bovill via use-
17 matches
Mail list logo
