Giter VIP home page Giter VIP logo

4d-mobile-app-server's People

Contributors

anass-talii avatar e-marchand avatar emmanuel-craeymeersch avatar htemanni92 avatar mesopelagique avatar vdelachaux avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

4d-mobile-app-server's Issues

Remove duplicate emails

if there is duplicate in email for push notification, could we remove it?

(maybe not if we found it by device them if too difficult, but if explicitly specify in email collection list)

ps: task to not forget

At least some push notification errors are not being returned

class PushNotification.send calls Mobile App Push Notification which calls apple_sendNotification.
In line 38-42 we have

If (Length($cmdPush_err)>0)
		
	LOG EVENT(Into 4D debug message; $cmdPush_err)
		
End if 

but, we don't return $cmdPush_err up the chain, so the PushNotification.result property is never set with the error, etc.

I ran into this issue, today. I got warnings, including a warning that a push notification was not sent (but no error), and I did not get a reason returned, either.

Literals do not pass the **value type** test for **badge** (ios)

The following code will not set the badge of a mobile app:

$notification:=New object()
$notification.title:="test title"
$notification.badge:=1

Discussion:

Inside of project method buildNotification on line 51, the value type of badge is evaluated:

If (Value type($1.badge)=Is integer)

Even the literal 1 evaluates to Is real in this code.
I tried a variety of workarounds to resolve this issue, including

$notification.badge:=Int(1)

but none of the things I have tried have worked.

Workaround:

The code does allow the developer to manually build a push notification using the userInfo object, however it cannot be used to supplement the other settings (like title and body, as it will overwrite other properties, so you cannot, for example use

$notification.title:="TEST PUSH"
$notification.userInfo.aps.badge:=1

because even though $notification.aps.title is initially set, using userInfo.aps will cause the code to wipe the other properties of aps instead of appending the aps.badge property.
However, you can build the entire aps object using this technique:

$notification.userInfo.aps.alert.title:="TEST PUSH"
$notification.userInfo.aps.alert.subtitle:="Test Subtitle"
$notification.userInfo.aps.alert.body:="test body"
$notification.userInfo.aps.badge:=1

Suggestions for resolving this issue:

In the buildNotification project method:

  1. Change line 51 to allow any numeric
  2. Change line 53 to:
$notification.aps.badge:=Int($1.badge)
  1. Change lines 98-108 so that it traverses $key and inserts $1.userInfo[$key] but does not wipe any existing property or object. This would make the code more future-proof since Apple is likely to modify the APNS Dictionary and Alert keys in the future.
  2. Keep publishing components as open source, so interested members of the community can dive into the code and help find this sort of issue. As an aside, it also helped me test my code, more, and discover that the previous issue I posted, this evening, was really a false alarm.

Filtrer les applis IOS en generant le well-known/assetlinks.json

  • Quand on jamais generé de app ios -> le package name est ok "com.myapp.test"

-mais une fois une app ios generé (et un team id remlpli = myteamidios) on se retrouve avec "package_name": "myteamidios.com.myapp.test" donc univesal links ne marche plus sur android

(Actuellement on a opté pour une solution provisoire : utliser app.application.id au lieu de app.id )

push only accepts email addresses for devices

Push is device-dependent, but sometime after b27545f (I have not dug into the code to discover where, yet), it became email-dependent. This might be fine for cases where only a personal device is being used, but it does not work at all for kiosks, where multiple people use the same device and the same person can be on multiple devices throughout the day.
In our case, we have the devices named, but the push code is now rejecting device names that are not email addresses.

"subtitle" field?

The docs describe and the code includes support for a subtitle property. However Apple's Docs does not mention it, and if I try to use it, the message does not make it to the device. Removing the key lets the message go.

Clarify when to use which option for instantiating a pushNotification

In the Instanciate the PushNotification class docs, several methods are mentioned:

  • none
  • Application ID
  • Bundle ID
  • Application Name
  • An object

Only none has an explanation as to why you would use it - namely, you only have one application folder in your MobileApps folder.
That leaves unanswered what differentiates the others.
It does not seem that they are different from each other, that they are all just different ways of matching the same folder names.

Remove usage of FOLDER LIST & DOCUMENT LIST

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.